Setting Up a Test Environment
Test Environment Setup: Overview
The ARM test environment enables efficient data transfer from CSV files into destination sandboxes, optimizing job execution times. This setup is particularly beneficial for validating data migration scenarios before performing a full-scale execution.
Step-By-Step Guide:
Navigate to the "DataLoader - Test Environment" by logging into ARM application.
Click on the "Create new job" button to initiate the job creation.
Select the required Org and click on the "Log and fetch objects" button to fetch the objects.
Observe the object list fetched and select the required object.
Click "Next" to continue to the "Source Data" section.
Either select the required file or drop the file onto the box to continue with the data import.
Drop the file
After adding the file, click upload file to upload the file
To indicate the progress of the upload, a progress bar will be displayed. On successfull upload, a success message will be displayed
Auto-Map Fields – Master Object
Under Master Object, click the Mappings icon for Account.
In Create Mapping: Account, click Auto Map to match like-named fields.
Use Search to locate specific fields if needed.
Save Master Object Mapping
Review the mapped Fields (Destination) and complete any unmapped ones.
Click Save.
Open Ancestor Object Mapping
Switch to the Ancestor Objects tab.
For each object (e.g., Opportunity), click the Mappings icon.
Auto-Map Fields – Ancestor Object
In Create Mapping: Opportunity, click Auto Map.
Verify mappings and manually adjust where required.
Save Ancestor Object Mapping
Confirm the field selections for the ancestor object.
Click Save.
Proceed to Process Details
Ensure the Success: Mappings saved successfully message appears.
Click Next to continue to Process Details.
Configure Job Details
In Create Test Environment Job → Process Details, provide a Job Name.
Select or enter a Job Group Name.
Click Save.
- Run Configurations
Disable Workflows
Temporarily deactivates Salesforce workflows during migration to prevent unintended triggers. Workflows are automatically re-enabled after migration completes.
Disable Validation Rules
Suspends validation rules to allow uninterrupted data migration. Rules are automatically restored once the migration is complete.
Use Bulk API
Leverages Salesforce Bulk API for handling large data volumes efficiently. Jobs can be executed in serial (sequentially, one after another) or parallel (simultaneously). For higher throughput, parallel mode is recommended.
Access Job Results
Under Actions for a job, select Job Results.
Open Validation / Workflow Rules
Click on the VR/WFR icon beside the object.
View Workflow/Validation Rules
The Validation / Workflow Rules panel opens.
Review Validation Rules under Name, Previous State, Current State, Enable, Error (if any).
Switch to the Workflow Rules tab.
Validate existing Workflow Rules or confirm that none are displayed.
Edit Object Mapping
Select the Mappings icon to open Edit Mapping.
Review source and destination fields.
Use Auto Map to match fields automatically, or manually map unmapped fields.
Click Save to update mappings.
View Job Run Results – Success
Under Results of Last Run, click the Success count icon.
A list of records with Destination IDs and Status: Item Created is displayed.
View Job Run Results – Failure
Under Results of Last Run, click the Failure count icon.
A list of failed records with Source IDs and corresponding Error Messages is displayed.
- Running a Job
Identify the desired job in the job list.
Click the Run button under the Actions column.
A configuration panel opens with the following options:
Disable workflow rules
Disable validation rules
Adjust the options if required, then click Run.
A confirmation message “Run Process Initiated Successfully” appears.
The job status updates to indicate that the process has started.
- Monitoring Job Execution
During execution, the job’s Status column updates to show the current progress.
Options available while the job is running:
View – Inspect job configuration or progress.
Stop – Terminate the execution if necessary.
Once completed, the status reflects success, failure, or warnings.
- Cloning a Job
From the job list, open the Actions menu (⋮ - three dots).
Select Clone.
A Clone Job panel appears where the following details can be updated:
Name – Defaults to original job name with -Copy appended, but can be edited.
Job Group – Assign to an existing group or create a new one.
Destination Sandbox – Select the target sandbox.
Click Clone to create the duplicate job.
The cloned job appears in the job list.
Open Bulk Actions
Click the Bulk Actions (three-line) icon at the top-right of the Test Environment list.
Bulk Actions Menu
Review available actions:
Run (disabled for bulk in this view)
Edit – bulk update job groups
Clone – clone multiple jobs at once
Delete – remove multiple jobs
Start Bulk Edit
From Bulk Actions, click Edit to open the bulk group editor.
Bulk Edit Job Groups
Use the Edit Job Group – All dialog to update the Category (group) for many jobs at once.
Optional: use Search to filter the list; navigate with Previous/Next or the page size selector.
Click Save to apply group changes, or Cancel to discard.
Start Bulk Clone
From Bulk Actions, click Clone to open the bulk clone setup.
Configure Bulk Clone
In Clone – All:
Group name (required) – Enter the target group for the new copies.
Destination Sandbox (required) – Choose where all selected jobs will be cloned.
Click Clone to create the copies, or Cancel to exit.
Start Bulk Delete
From Bulk Actions, click Delete to open the selection panel.
Select Jobs to Delete
In Category: All, select individual jobs or use the header checkbox to select all.
Click Delete to permanently remove the selected jobs, or Cancel to keep them.
Last updated
Was this helpful?