Swap a development environment with another development environment. If your development
environment is a Developer or Developer Pro sandbox that was recently refreshed, the connection to
the existing environment is no longer valid. You must swap the sandbox to reestablish the
connection to it in DevOps Center.
Required Editions
Permission Sets Needed
To swap an environment:
DevOps Center Manager
To access the named credentials required to authenticate to the environment:
sf_devops_InitializeEnvironments
Important We recommend that all sandboxes are refreshed from your production
(release environment), or cloned from a pipeline stage or an existing development
environment.
Before you swap the dev environment, keep these things in mind:
We recommend that you promote all work items before refreshing the sandbox.
When you refresh the sandbox, you lose any changes in the current environment that
weren’t pulled and committed to work item feature branches in the source control
repository.
Any changes in the old sandbox that were pulled and committed, but not promoted,
are in the work item’s feature branch but aren’t visible in the new sandbox. To view the
committed changes in the new sandbox, promote the affected work items and then perform a sync
from the first pipeline stage’s branch back to the sandbox. See Synchronize Your Development Environment for details.
The DevOps Center connection to the current environment is no longer usable.
The new dev environment must have source tracking enabled.
In the Pipeline Environments tab, select Swap Environment from the
environment’s menu.
Click I Understand to acknowledge the considerations, then click
Continue.
Select Log In to New Environment, then click Log
In.
Complete the login process.
After the swap is complete, check to see if the development environment is out of sync. If so,
we recommend synchronizing the environment before continuing work.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
