Mapping Generation
The progress of the mapping generation is displayed as shown below
Creation of Reference Mappings (Service Now Instance Migration Only)
If any reference tables were selected, tasks will be added to create disabled mappings to support the reference mappings that that will ensure that the sys_id stored by the reference field is updated to the sys_id of the same target record, correlating using the defined display field for the form.
Note that if a mapping with key mappings defined already exists in the project for the referenced table, the existing mapping will be used instead of creating a new one.
Example of use:
the incident form contans a field assigned_to. This holds the sys_id of a user. However on the target server, the same user exists, but with a different sys_id. By selecting sys_use as a reference table, Precision Bridge will create a disabled form mapping for sys_user, with the key mapping set to the display field (user_id)
Any Reference type field in the tables selected for mapping that have fields referencing sys_user (e.g assigned_to on the incident table) will be mapped using a reference mapping that makes use of the disabled form mapping.
Creation of Custom Tables and Fields
Next, tasks run will be to create any missing custom tables/fields if these options were selected in the options tab.
If there are any errors during this process, the task will report the failure, but this will not prevent the remainig tasks from continuing.
Cache Refresh
This task will be performed if any new tables of fields were added in the tasks that created custom tables and fields. It will ensure that the newly added tables/fields are visible to Precision Bridge when the Form Mappings are created.
Creation of Form Mappings
Finally, mappings will be added for each selected form, in the order they were listed. Note that a new mapping will be added even if a mapping for the selected form already exists in the project.
- A source filter will be added if:
- a Parent was selected for the form in Mapping Options. In this case, an inclusion filter is added to ensure that only records where the 'parent' record was migrated are included.
- the form is extended by other forms (in this case a filter is added to prevent records for extended tables being migrated)
- The Is Delta Project is selected. In this case a filter is added to ensure that only records migrated since the last migration (given by the LAST_EXECUTION_TIMESTAMP project variable)
This process can take some time if many forms are included, particularly if the forms have many fields.
Cancelling the Process
Clicking 'Cancel' will stop the generation process, but will not remove any form mappings that were already added.
Saving the Definition
If you would like to save this definition to re-load for use at a later date, you can do so.
Comments
0 comments
Please sign in to leave a comment.