You are here:
Data 360 in a Scratch Org
Use scratch orgs to develop and test Data 360 features alongside your Salesforce CRM customizations. Scratch orgs help teams work in parallel, identify configuration issues before deployment, and include Data 360 development in an existing Salesforce development lifecycle.
Required Editions
Changes that you make in a scratch org don't modify the metadata or configurations in your production org or sandboxes. However, Data 360 usage in a scratch org can consume credits associated with the Dev Hub's production account.
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
What Is a Scratch Org
A scratch org is a temporary Salesforce environment that you create from a Dev Hub. Its configuration is defined in a scratch org definition file, and you populate it with metadata and data from your development project.
Use scratch orgs to:
-
Develop features in parallel without creating configuration conflicts.
-
Test Data 360 and CRM metadata together.
-
Run automated tests.
-
Validate configurations before packaging or deploying them.
-
Reproduce issues in an isolated environment.
A scratch org expires after seven days by default. When you create it, you can specify a duration of up to 30 days. You can't extend its lifespan after Salesforce provisions it. Your Dev Hub can be a production org or, for Salesforce partners, a Partner Business Org (PBO). Enable Dev Hub before creating scratch orgs. The Dev Hub edition determines the number of active and daily scratch orgs available to your team. For details, see Supported Scratch Org Editions and Allocations.
How Data 360 Works in Scratch Orgs
To provision Data 360 in a scratch org, add the appropriate Data 360 feature to the scratch org definition file. Salesforce provisions Data 360 capabilities alongside the CRM capabilities defined for the scratch org. Store your Data 360 and CRM metadata in source control so that your team can create consistent development environments. Data and configurations that exist only in a scratch org become unavailable when the org expires.
Billing Considerations
Data 360 activity in a scratch org can consume credits associated with the Dev Hub's production account. You can review eligible usage in Digital Wallet.
Confirm the applicable usage rates and billing terms for your contract before using scratch orgs for high-volume testing.
- Create a Data 360 Scratch Org
Create a scratch org to use Data 360 configurations in your development workflow. A scratch org is a temporary, source-driven Salesforce environment tailored for developing and testing specific features. This step enables Data 360 and related features in your scratch org. Use it to build and validate your configurations without affecting your production org or sandboxes.
