Lightning Communities Developer Guide

Get Up to Speed with Lightning Communities
Develop Lightning Communities: The Basics
Customize the Look and Feel of a Lightning Template
Example: Build a Condensed Theme Layout Component
Develop Secure Code: LockerService and Stricter CSP
Analyze and Improve Community Performance
Connect Your Community to Your Content Management System
Community Migration, Packaging, and Distribution
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Upload 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.

User Permissions Needed
To create, edit, or upload outbound change sets: Create and Upload Change Sets

Watch a Demo: Watch Video Demo Release Management: Deploying Changes Using Change Sets (Salesforce Classic)

A change set can have up to 10,000 files with a total file size of 400 MB. Change set components are represented as metadata XML files. Make sure that your change set doesn’t exceed approximately 5,000 components.

Note

Sending an outbound change set to another org doesn’t guarantee that the changes are implemented in that org. The change set must be deployed by the target org before the changes can take effect.

To help ensure a smooth deployment, review information about permission sets and profile settings in change sets.

Tip

After you upload a change set, its status becomes closed, and you can’t make changes to its components. Also, the components in a closed change set don’t get refreshed. To redeploy the same set of components, clone the change set. The cloned change set includes the latest changes to its components source. You can add and remove components in the cloned change set. Cloning change sets is helpful during the iterative phases of a project.