Migrate Parent/Child Records Using Target / Bulk Loader
Last updated
Last updated
appRules features an unmatched number of options for migrating, replicating and synchronizing data.
The "Migrate Parent/Child Records Using Target/Bulk Loader" sample project demonstrates another option for executing parent/child migrations and features the following:
The InitializeTarget workflow activity activated for Bulk Loading
The MapRecordFields activity used for mapping, inserting records and record iteration
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
| Platform Product | Availability |
|---|---|
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Migrate Parent/Child Records Using Target / Bulk Loader" project.
This sample project demonstrates how to use only a few activities to migrate parent/child records.
The sample migrates records from a Customer table in a SQL database to the Account and Contact tables in Salesforce. You must set the authentication properties for Salesforce before running the project.
Reads records from the Customers table of the SQL database to be imported into the Salesforce Account and Contact objects.
Initialize target for the Salesforce Account records. Customer company records will be stored using this activity.
Initialize target for the Salesforce Contact records. Customer contact records will be stored using this activity.
The while loop activity is used for iterating the records in the Customer table and mapping accounts/contacts, and specifying the Save options. It contains the two MapRecordFields workflow activities used in the project.
Maps Customer record using company fields to Salesforce Account record. After mapping, the record is saved using this activity.
Maps Customer record using company fields to Salesforce Account record. After mapping, the record is saved using this activity
| Hosting Option | Recommended for Project |
|---|---|
appRules Data Migration Engine
appRules Integration & Automation Engine
appRules Enterprise 360
IIS
appRules Host Service
appRules Desktop
