With 海角天涯社区鈥檚 data loader you can deploy test data between your orgs. That testing becomes much more effective when you鈥檙e confident about what data you鈥檙e using for your tests.
Our new data deployment templates let you save and re-use the configuration after a data deployment. Re-using a configuration lets you perform repeatable data deployments, so you can be sure of the data that you鈥檙e testing with.
Salesforce DevOps in the age of AI: is your custom pipeline ready?
What are data deployment templates?
It鈥檚 helpful to have some realistic data to test your changes with. 海角天涯社区鈥檚 data loader lets you deploy data to an org, but there鈥檚 a lot of configuration:
- which types do you want to deploy?
- how many records do you want to deploy?
- do you want to filter which records you deploy?
- what are the relationships between the types?
This configuration lets you be specific about which records you want to deploy, but it鈥檚 easy to miss an important record or make a mistake. This could mean that your tests aren鈥檛 based on realistic data, which could lead to changes failing in production.
With data deployment templates you can save this configuration. This lets you do repeatable deployments, giving you confidence in your test data. Using a template should also save you some time!
How do I use a data deployment template?
Before you can start using data deployment templates, you鈥檒l need to create one. When you complete a data deployment, you can save the configuration as a new template. This saves all the configuration for that deployment.
Next time you do a data deployment, you can select a template to use for that deployment. This will apply the configuration from the saved deployment so you can speed through the deployment and start your testing.
You鈥檒l be able to select any template that you or members of your team have created.
Managing data deployment templates
You can rename or delete a template by clicking the settings icon on the Configure data deployment page. You can only rename or delete templates which you created.
Limitations
In some cases objects or fields from the template may not exist. This could happen if you鈥檙e deploying between different source and target orgs from the orgs used to create the template. A field used as an external ID which has been deleted from the target causes the same problem.
When 海角天涯社区 can鈥檛 use the full configuration from the template it will apply as much of the template as possible. It won鈥檛 include objects or fields that don鈥檛 exist. For any external ID fields that don鈥檛 exist, 海角天涯社区 will default to the same field it would use if you weren鈥檛 using a template.
What benefits do I get from data deployment templates?
Data deployment templates bring the usual benefits of automating a process:
- it鈥檚 harder to make mistakes through human error
- it saves you time by letting you specify the configuration once and re-using it
- it gives you confidence that the deployment will be the same every time
This means that you can spend less time deploying data to an org and focus more on testing the org.
Happy deploying!
Whether you鈥檙e sandbox seeding or migrating data between orgs for any other reason, we appreciate that data deployments can be tough. For guidance on establishing a seamless deployment process in your orgs, book a consultation with one of our DevOps experts.
Or to try our quick and repeatable data deployments for yourself, start a now with nothing to install in your orgs.
