Working with Sandbox

Working with Sandbox

Rebuilding a sandbox

Note: Rebuild was earlier referred to as refresh
When your Sandbox setup is not in sync with the Production setup, any testing that you conduct in Sandbox will not be relevant when deployed to production. So it is important that you always update Sandbox by using a Rebuild Sandbox option. This ensures you have the latest production configurations and data in your sandbox.  
Note: Upon rebuilding the sandbox only changes made to the configuration is updated, data is not transferred from the production to the Sandbox account. During every rebuild, populated data will reload newly.

Points to remember 
  1. You can rebuild the sandbox created for 
        (i) Configuration and Data type only once in 3 days,
        (ii) Configuration type only once in a day
  1. Any changes made in the Sandbox settings which is not yet deployed to Production will be lost when you rebuild the Sandbox. All settings will be replaced with those in the Production setup.
  2. Data and settings done to the Sandbox will be lost if not already deployed to the production account. 
  3. Changes deployed from Sandbox over the last 6 months will be displayed under Deployment Logs.
  4. Trial edition users cannot rebuild the sandbox. 
  5. Once you have deployed changes to production, remaining changes in the  Change set will be retained until the next rebuild.

To rebuild Sandbox
  1. Go to Setup > Data Administration > Sandbox.
  2. Click the Rebuild Sandbox button on the top right.
     


Editing a sandbox

Users with Manage Sandbox permissions can edit the configuration. They can change the name and description and add or remove users who can access the sandbox. 
Note that the fields, sandbox type, and data to be populated can only be modified and saved if the Rebuild Sandbox option is available. 
To edit a sandbox
  1. Go to Setup > Data Administration > Sandbox.
  2. Click the sandbox you want to edit.
  3. Click the  icon from the top right corner and click Edit.
  4. In the Edit Sandbox popup, make the necessary changes.

Setting a default sandbox

Users and Developers who have access to  more than one sandbox account  can set a  default account for themselves. This also helps users to switch between different sandbox accounts easily. 

To set a Sandbox as default,
1. In the CRM account, click the profile on top-right corner.
2. Click the sandbox dropdown and click Manage
3. In the screen, hover to the sandbox under Organization list and click Set as default.


Deactivating a sandbox

There might arise situations where you do not need a sandbox for a period of time. For instance, your organization is undergoing major automation changes, sales restructure etc. and you do not want the users and developers to test admin related changes in the sandbox temporarily. At the time  you can  deactivate the sandbox account  . 

Only those CRM users who have access to the Sandbox account can deactivate it.  Upon deactivation developers and other users will not  be able to access the account. 

Points to remember
  1. Changes to the production account cannot be deployed until the account is reactivated .
  2. When the sandbox is reactivated, all the un-deployed changes which were listed in the Change Set before deactivation will be retained. The retained changes can be deployed them to production.

To deactivate Sandbox
  1. Go to Setup > Data Administration > Sandbox.
  2. Click the sandbox you want to deactivate.
  3. Click the   icon from the top right corner and click Deactivate.
  4. Click Deactivate to proceed with the deactivation of your sandbox.

Alternately, you can toggle the Status from the  Sandbox list page. 
           

Deleting a sandbox

You can delete the sandboxes that you no longer need to test or once the changes are deployed to the production. Users with Manage Sandbox permission can delete sandbox.

To delete a sandbox
  1. Go to Setup > Data Administration > Sandbox.
  2. Click the sandbox you want to delete.
  3. Click the   icon from the top right corner and click Delete.
  4. Click Delete to proceed with the deletion of the sandbox.

Alternatively you can delete it from the Sandbox page, by clicking the delete icon next to the sandbox name.
           
           
Note:
The developer and the CRM users will not be able to access a deleted sandbox.

    • Related Articles

    • Deploying sandbox changes to production

      Sandbox mimics your production environment, allowing you to test real-time business scenarios with CRM data and deploy the configurations from sandbox to production without any impact on the original data.  Examples: Create a blueprint, simulate a ...
    • Creating Sandbox

      Creating  sandbox account CRM admins can create multiple sandboxes in one account to test different configurations independently. While creating a sandbox you need to do the following: 1. Choose the sandbox type: There are two types of sandboxes to ...
    • Sandbox Overview

      As your organization grows so does the complexity in your sales processes. At such a juncture, any small error in a process could have a domino effect. No organization can afford such a situation. To help overcome this hassle, Zoho CRM offers ...
    • Can I create multiple sandbox accounts using multi-org feature?

      Yes, a CRM user can create up to 10 sandbox accounts and be a Super Admin in up to five accounts. Any CRM user who has the permission to create sandbox can create upto 5 accounts. Read more about creating multiple CRM accounts. Refer to this page to ...
    • Using multi-org feature I am unable to create a sandbox account, why is that?

      The possible reasons for not been able to create Sandbox account could be: You may not have create permission in the production CRM org. You are already part of 10 sandbox orgs. You are already super admin in 5 sandbox orgs.