Using a Full Data Sandbox
A Vault CRM Full Data Sandbox is a complete, isolated replica of your Vault CRM production environment. It includes all configuration, metadata, and application data, enabling teams to develop, test, and train in an environment mirroring production. Customers who want a sandbox version of their production Vault CRM instance can request a Full Data Sandbox. Customers who already have a Full Data Sandbox can refresh it to reset the configuration and data to match production.
The Full Data Sandbox:
- Includes all Vault CRM application data, metadata, configuration settings, and object relationships from production are cloned, offering a true-to-life environment for realistic testing and training
- Functions independently of production to prevent unintended impacts. Changes made in the sandbox do not affect live customer data or workflows.
- Can be refreshed on a defined cadence (for example, monthly or quarterly) to sync with the latest production state
- Can be reset as needed to specific snapshots or initial states
If the production Vault CRM instance is connected to other Vault applications, for example, PromoMats/MedComms or Vault RIM, ensure the Full Data Sandbox is also connected to those applications.
Considerations Before Requesting or Refreshing a Full Data Sandbox
Before requesting a Full Data Sandbox, be aware of the following considerations and behaviors:
- A Full Data Sandbox cannot be used immediately after creation. The process to create a Full Data Sandbox can take days depending on the number of records in the production Vault instance. Customers must activate users and ensure their data is set up correctly, for example, by managing licenses and integrations.
- Full Sandbox functionality creates users with .sbx prefix in the sandbox domain. For example, if in Production the domain username is john.smith@domain.com, the full sandbox will create a user with the username john.smith.sbx@sbx-domain.com.
If a Sandbox user’s email address is changed for testing and training purposes, ensure the email address is set back to the value in Production before requesting a Full Data Sandbox refresh. Changing the email address of an existing user and failing to change it back before the refresh causes issues the next time a refresh of the Full Data Sandbox is requested.
- Most records in the Full Data Sandbox do not maintain the same IDs as in production. However, some features depend on text fields populated with record IDs. The Full Data Sandbox creation process replaces IDs in the text fields of the following objects:
- account_territory__v
- user_territory__v
- account_territory_loader__v
- child_account__v
- tsf__v
- view__v
The process does not replace IDs for other objects.
Requesting or Refreshing a Full Data Sandbox
To request or refresh a Full Data Sandbox, submit a support ticket with the following information:
- The customer name and the Vault ID of the production Vault instance to copy
- Whether you want to create a new Full Data Sandbox or refresh an existing Full Data Sandbox.
- The name of the Full Data Sandbox you want to create or refresh
- The username of one production user to activate in the Full Data Sandbox when the process is complete
Customers are only allowed one Full Data Sandbox per production Vault instance.
Requesting a Full Data Sandbox is different from the out-of-the-box platform functionality of administering sandbox Vault instances. Using the out-of-the-box functionality to administer a sandbox Vault instance copies the configuration of the production instance, without the data. For information on the objects and records copied during the platform process, see How Configuration Copying Works.
