An inbound change set is a change set that has been sent from another
Salesforce org to the org you are logged in to. A change set must be deployed for
the changes to take effect. You can deploy the contents of an inbound change set as a whole but
not on a component-by-component basis.
Required Editions
User Permissions
Needed
To deploy inbound change sets:
Deploy Change Sets AND Modify Metadata Through Metadata API Functions
Validate a Change Set You can validate a change set without deploying changes. By validating you can view the success or failure messages you receive with an actual deploy.
Deploy a Change Set You can deploy the contents of an inbound change set as a whole but not on a component-by-component basis.
When Change Sets Become Unavailable A change set deployed from a source sandbox that you recently deleted or refreshed can temporarily appear available for deployment in the target org.
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.