Seed Relational Data via Pipeline

Follow these steps to create a Pipeline and the Executables using the Migration Builder for migrating relational data through dedicated chained batch jobs.

• Naviage to the "Current => Org B" Direction where the source is the current org and the target is Org B.
• Click "New Pipeline" from the related list, name it as "Seed Relational Data".
• Naviage to the Migration Builder tab, and follow the below steps to create Executables for migrating relational objects:
  • Select root object: Account
  • Select Cascade criteria to child objects checkbox.
  • Expand nodes in sequence: Account -> Contact -> Case.
  • Select the leaf node: Case.
  • In the popup modal, set the mappings for Source & Target Objects, and the Matching Fields.
  • Close the popup modal, add criteria to the source Account object, and validate: Is_Test__c = TRUE
  • Click Create Executables button to generate Executables in sequential order aligned with the object hierarchy.
• Navigate to each Executables and Verify the Retrieve Criteria and Field Mappings, expecting:
  • Is_Test__c = TRUE is added to child objects in cascaded manner.
  • For Record Type, DSP uses the Source Object's RecordType.DeveloperName to maintain the relationships in the target, given the same Record Type exists in the Target Object.
  • For regular reference fields, DSP uses External ID Field to maintain data relationships.
  • All non-reference fields are automatically mapped if the target and source objects have the fields with the same fields and compatible data types.
• Click Execute Batches to execute the batch jobs in chained order.
• Click any Execution link to inspect the execution details, if required, click Re-Execute Failed Batches to restore the migration from the failed Batch Execution logs.
• Verify the data created in the target org, especially for the data relationships.