Loading
Sandboxes: Staging Environments for Customizing and Testing
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Change Sets

            You are here:

            1. Salesforce Help
            2. Docs
            3. Sandboxes: Staging Environments for Customizing and Testing

            Change Sets

            Use change sets to send customizations from one Salesforce org to another. For example, you can create and test a new object in a sandbox org, then send it to your production org using a change set. Change sets can contain only modifications you can make through the Setup menu. For example, you can’t use a change set to upload a list of contact records. Change sets contain information about the org. They don’t contain data, such as records.

            Required Editions

            Available in: both Salesforce Classic and Lightning Experience
            Available in Enterprise, Performance, Professional, Unlimited, and Database.com Editions
            User Permissions Needed
            To edit deployment connections:

            Deploy Change Sets

            AND

            Modify Metadata Through Metadata API Functions
            To use outbound change sets: Create and Upload Change Sets
            To use inbound change sets: Deploy Change Sets AND Modify Metadata Through Metadata API Functions
            Note
            Note To deploy metadata and configuration simulateneously, use DX Inspector. See Deploy Metadata and Data from DX Inspector.

            When you want to send customizations from your current org to another org, create an outbound change set. After you send the change set, the receiving org sees it as an inbound change set.

            Sending a change set between two orgs requires a deployment connection. Change sets can only be sent between orgs that are affiliated with a production org. For example, a production org and a sandbox, or two sandboxes created from the same org can send or receive change sets.

            • Permission Sets and Profile Settings in Change Sets
              Developers can use permission sets or profile settings to specify permissions and other access settings in a change set. When deciding whether to use permission sets, profile settings, or a combination of both, consider the similarities and differences.
            • Components Available in Change Sets
              The components available for a change set vary by experience and edition. Also, some components require corresponding features to be enabled in your Salesforce org.
            • Restrictions for Approval Processes in Change Sets
              Understand these restrictions before you include approval processes in change sets.
            • Change Sets Implementation Tips
              Review these tips before you implement your change sets.
            • Change Sets Best Practices
              Review these best practices about dependencies, validation, and access settings.
            • Inbound Change Sets
              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.
            • Outbound Change Sets
              An outbound change set is a change set created in the Salesforce org in which you are logged in and that you want to send to another org. You typically use an outbound change set for customizations created and tested in a sandbox and that are then sent to a production org.

            See Also

             
            Loading
            Salesforce Help | Article