Avoid common mistakes by reviewing these considerations before setting up a Data Cloud One cluster. Create sandbox orgs from your production orgs before establishing Data Cloud One connections, or clean up Data 360 metadata before recreating your Data Cloud One cluster. You can’t use Data Cloud One to connect a sandbox org to a production org.
We recommend first creating sandboxes orgs from your production orgs, then creating Data Cloud One connections. Your connections aren't copied to sandbox orgs. You can't reestablish a Data Cloud One connection until you've cleaned up copied Data 360 metadata from the sandbox companion org.
To create a Data Cloud One sandbox, activate the Ingestion API connector and make sure the remote_connection_full-sync_feed and remote_connection_incremental-sync_feed data streams are active.
What Copies to a Sandbox and What Doesn't
These items are copied to sandbox orgs.
- Data 360 and Data Cloud One Companion Org licenses
- Data 360 metadata
These items aren't copied to sandbox orgs. Manually add or create them.
- Data 360 data
- Data Cloud One companion connections
Because Data 360 data isn’t copied into your sandbox orgs, we recommend populating your sandbox orgs with sample data. Using a small set of representative data lets you save on data processing costs while testing your configurations.
Best Practices for Setup and Maintenance
- Create or refresh Home and Companion sandboxes as close together in time as
possible.
The closer together they're created or refreshed, the smaller the chance of metadata drift between them.
- Establish Data Cloud One companion connections immediately after creation of the
sandboxes.
Connecting right after creation further reduces the likelihood of metadata drift.
- Don't delete Data 360 metadata on the Home sandbox org before
connecting sandboxes of its companion orgs.
This is especially important for metadata that the companion org depends on. If you delete the metadata on the Home sandbox first, there is a higher chance of metadata drift, and you'll need to delete the drifted entities on the companion sandbox before the connection can complete.
- Manually activate Data 360 on your Home org sandbox.
Data 360 doesn’t turn itself on in sandbox orgs. To turn it on, go to Data Cloud Setup Home.
- Disconnect companion sandbox orgs from home before refreshing them.
Refreshing a sandbox completely destroys the existing org and generates a new org ID, which breaks your Data Cloud One connection but doesn’t remove it. Log in to your Home org and go to Data 360 Setup to disconnect the companion org, then reestablish the connection.
- Match production org licenses.
If you license Data Cloud One companion orgs after setting up sandboxes, add the Data Cloud One Companion Org license to your sandbox by matching production licenses.
Cost Considerations in Data 360 One Sandbox Orgs
When you use Data 360 data services or other services that consume credits, credits are decremented from your production Home org’s consumption cards. Usage is discounted in sandbox orgs.