One-To-Many Migration
The "One-to-Many Migration" option is used for migrating data from a single Source data record to multiple Target data records (SecondaryEntities). The records can also be linked to create parent/child relationships.
To perform "One-to-Many Migration" using the appRules Data Migration Engine, drag-and-drop the MigrateData workflow activity from the toolbox on to the designer and configure as follows:
Enter a display name and description for the workflow activity or accept the defaults.
Select "One-to-Many Migration" as the Data Migration Type.
Select the Default Source. If the Source data source does not exist, you can use the New Data Source button to add it.
Select the Default Target. If the Target data source does not exist, you can use the New Data Source button to add it.
Click the OK button to accept the entries and continue.
The "Initialize One-to-Many Migration" modal will be displayed:
Initialize the "One-to-Many Migration" option by configuring the fields as follows:
Select the Source entity/table to be migrated.
Select the primary target entity.
Select the secondary target entities.
Click the OK button to accept the entries and display the Target Entities Collection.
Target Entities Collection
Note that the system automatically generates entries for the secondary entities in the Target Entities Collection.
Refer to the Target Entities Collection section for notes on configuring the target entities including the secondary entities.
Run your data migration project after configuring, reviewing, and saving the Target Entities Collection.
Review the One-to-Many Migration sample project to learn more about how to create "One-to-Many Migration" projects in appRules.
Last updated
