Sandbox Refresh

Updated 1 year ago by Copado Solutions

Whenever a sandbox is refreshed, you need to perform the following steps:

  1. Get the new org id of the refreshed sandbox. Go to Setup -> Company Information -> Organization Id field:
    1. If the org id has only 15 characters, convert it to 18 characters. You can do this using this tool.
  2. Open the Environment record:
    1. Update the Org Id field with the new org Id.
    2. Notify the owners of these org credentials so that they authenticate them again, since the previous OAuth token is no longer valid.

Branch Management - Steps for Refreshed Sandboxes

  1. Go to your Git repository service:
    1. Create a new branch out of the branch that is linked to the sandbox. This branch will be a backup branch to review any commit history in the future. It is recommended to add the current date in the name of the backup branch.
      E.g. If your sandbox branch is named dev1, then the name of the backup branch will be dev1_backup_MM/DD/YYYY.
    2. Delete the branch linked to the sandbox (e.g. dev1).
    3. If you are cloning your new sandbox out of production, create a new branch out of master and name it with the same name as the branch deleted in the previous step. If you're cloning your sandbox out of another sandbox, then create a new branch out of that parent sandbox's branch.
      If your branch has a different name, you will need to edit the Git Snapshot record linked to the previous branch. Remove the branch name from the Branch field and add the new name.

How did we do?