Generate Form Mappings for Same Server Type Migration - Mapping Properties

Here, you can:

• Specify parent/child relationships
• Optionally Include Attachments in the migration
• Change the ordering of the form mappings

Defining Parent/Child Relationships

These will be implemented using an inclusion filter in the generated mappings. See here for more information on inclusion filters

To perform this action:

• Double click any available row to display a dialog used to specify the parent field and parent table that will define this relationship.

• The Parent Table will display a list of all selected source forms that are ABOVE this one in the list and can therefore be a 'Parent'.

• The Parent Field will display a list of fields on the source form that have a string, reference, or list type. Select the field that references the parent table (see example below)

• In the dialog, clear both the fields and click 'OK' to remove a parent/child relationship.

Parent Child Mapping Example

The use case is to migrate all incident records (optionally within a date range) and all journal entry records associated with ONLY the migrated incidents.

In this example, Incident is the Parent, and Journal Entry is the Child

The field in the Journal Entry that holds the sys_id of the parent incident is Element ID

This will result in the following inclusion filter being added to the Journal Field mapping to ensure that only journal entries for the migrated incidents are included.

Include Attachments Option

Specify whether attachments should be migrated for each table by checking the checkbox in the attachments column. Note that attachment migration takes additional time (even if there are no attachments found) so only select this option where attachments might be found on the migrated records.

Change the Sequence of Form Mappings

Use the up/down buttons to the right of the table to move a selected mapping up or down in the list. The order will specify the order that they are added to the project and ultimately, the order of migration when the project is executed.

Note that for Parent/Child relationships to work, the parent must be migrated BEFORE the child.

Next Step:

Once you have defined any parent/child relationships between tables and identified which mappings should include attachments, move to the Reference Mapping section, if supported by your source/target platform or Options section if not.