After validating and approving your changes, deploy them to the production environment.
You can deploy only one change set at a time. The prior deployment must complete before you can
deploy another change set.
Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning
Experience
Available in: Enterprise, Unlimited, and Developer
Editions
Available for an additional cost in: Professional Edition with Web
Services API Enabled
User Permissions Needed
To deploy change sets in Salesforce Spiff:
A Spiff user role with these permissions turned on.
Change Sets: View
Change Sets: Deploy
Note To prevent data collisions, you can’t modify the target environment or access Designer
while a deployment is in progress. Because you can’t undo a deployment after it starts, verify
all changes before you begin. You can’t deploy change sets from multiple sandboxes to a single
parent environment.
In the parent environment, go to Admin and select
Settings.
Under Environments, select Inbound Change Sets.
In the Name column, click the change set to deploy.
You can only deploy a change set that you’ve approved and with the status Ready to
Deploy.
Click Deploy Changes.
After you deploy a change set, go to Spiff Designer in the parent environment and wait for
the page to load.
Accessing Designer is necessary to trigger the remapping of formulas and to ensure
calculations run correctly. The deployment isn’t finalized until you complete this step. After
you deploy a change set to the parent environment, you can’t revert the changes.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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.