Test Environment Setup
Test Environment Setup: Overview
This enables data transfer from .csv files to the destination sandbox more conveniently and reduces run time using a test environment.
Create a New Test Environment Setup
Hover your mouse over the
Dataloader
module and selectData Loader Test Environment Setup
.Click on
Create New Job
.On the next screen, select your
Destination Org
.Click
Login and Fetch Objects
. This lists all the objects available in your destination org.Select one of the objects from the list of objects being displayed. Here, we will call this object the
Master Object
.To view the dependencies of the master object with respect to its parent object, click on the
Show Dependencies
icon.
![](https://knowledgebase.autorabit.com/~gitbook/image?url=https%3A%2F%2Fcdn.document360.io%2F8711f4e7-c040-4616-aac9-d947f87e4619%2FImages%2FDocumentation%2Fimage-1656499789815.png&width=768&dpr=4&quality=100&sign=ecf931cf&sv=1)
Click the
Switch to Graph View
button to view the same report in the graphical format.Under the
Source of data
section, upload the CSV file from your local machine in zip format.
Important Note: Upload the zip file containing object-related CSV with a .csv file name equal to the object API name. Having parent objects related to CSV in the zip file is optional. But records from those objects are migrated if and only if respective CSVs are uploaded.
In the
Job Details
section, give the job aName
.Select the category from the
Job Group
field. This is important to arrange related jobs into a single category.Master Object
andExternal ID
details are auto-populated.Click
Save
.The user is redirected to the
Test Environment Setup summary
page, where your recently created job is displayed at the top of the list.Click
Run
to initiate the job.
The below table lists the deployment criteria for your job:
Configurations | Descriptions |
---|---|
| All the workflows of the Salesforce objects are deactivated, and the data is transferred from the source to the destination sandbox. Once the migration is complete, workflows are reactivated. |
| Validation rules verify that the data a user enters in a record meets the criteria you specify before the user can save the record. On selection, all the validation rules of the Salesforce objects are deactivated, and the data is transferred from the source to the destination sandbox. Once the migration is complete, validation rules are reactivated. |
| The Bulk API is based on REST principles and is optimized for inserting, updating, and deleting large data sets. You can use the Bulk API to process jobs in serial or parallel mode. Processing batches serially means running them one after another, while processing batches in parallel means running multiple batches simultaneously. Note: When you run a Bulk API job, processing more batches in parallel means giving that job a higher degree of parallelism, giving your overall run better data throughput. |
![](https://knowledgebase.autorabit.com/~gitbook/image?url=https%3A%2F%2Fcdn.document360.io%2F8711f4e7-c040-4616-aac9-d947f87e4619%2FImages%2FDocumentation%2Fimage-1656503628599.png&width=768&dpr=4&quality=100&sign=f4dd3850&sv=1)
Click
Run
.
Edit:
Allows users to modify the process details according to their requirements.Delete:
Deletes a process.Clone:
Creates a copy (clone) of the selected process.Log:
Provides information about the execution of a process.
Schema (Grid View)
This section lets you view the master object and its related information for the test environment setup job. For the setup run with disabled validation/workflow rules, ARM lists all the validation rules set under VR/WFR
section. The UI lists all the workflow/validation rules; users must enable them for the disabled rules (if required).
Last updated