Using ID Mappings Derived from Earlier Form Mapping

This option should be used if you have a previous form mapping in the same project with the same source and target form/table and you want to update the records previously migrated.

Use the Previous Form Mapping drop-down to select a form mapping with the same source and target form/table.

Note that if you have selected the Import Set (Scripted) migration method with migrate Sys-Ids option, this will take precedence and update any record found with a matching Sys-Id.  Otherwise it will use the key mappings from the previous form mapping to identify the target record for updating.

If no matching record is found then the No Match Action is followed:

Create New	A new record is inserted.
Skip Record	No update is performed and the record is skipped.
Log Error	No update is performed and an error is recorded in the migration report.

If the original form mapping is disabled then the No Match Action will apply to all records.

The diagram below provides a summary of the logic applied when the Use ID Mapping Derived from Earlier Mapping option is selected.