Published at: 2025-10-30
Outbound Change Sets
1. Outbound Change Sets
Outbound change sets are collections of metadata packaged in this environment and sent to a linked external environment.
1.1 Create an Outbound Change Set
Click the Create Change Set button. Enter a name for the outbound change set to open its detail page, then click Add Components to include metadata components in the change set.
The Add Components page displays all metadata components in your organization. Select the metadata you want to include in the change set.
When adding components, confirm whether you also need to include components that are related to the ones you selected.
For example, when adding a custom field, verify whether the object that owns that field must also be included in the change set.
If the target organization where you deploy this change set does not have the owning object and the change set does not include that object, the deployment will fail.
1.2 Upload an Outbound Change Set
After adding metadata components to the change set, upload the change set to the linked organization for deployment.
Click the Upload button on the list or detail page to start the upload.
-
Change sets have the status Pending Upload before they are uploaded. Components in a Pending Upload change set reflect the current metadata state in the environment and will update if the environment’s metadata changes. > Example: You add custom field A (type: text, length: 20) to an outbound change set. Before the change set is uploaded, someone changes field A’s length to 30; the change set will reflect length 30.
-
After uploading, the change set status becomes Closed. Components in a Closed change set do not update when the environment’s metadata changes. > Example: You add custom field A (type: text, length: 20) to a change set and upload it. Later someone changes field A’s length to 30 in the environment, but the change set still contains length 20. You also cannot add or remove components from a Closed change set.
-
When you select certain component types for an outbound change set, the system automatically packages related components and includes them in the change set. After upload, these automatically included dependent components appear in the change set’s component list.
-
The automatic dependency rules for outbound change sets are listed below:
| Selected Component Type | Automatically Included Related Component Types |
|---|---|
| Object | Related Import Settings, Layouts, Validation Rules, Fields, Record Type |
| Field | Related APL code, Global Variables, Shared Picklists |
| Button | Related APL code, Object Mapping Rules |
| Layout | Related APL code (UI events). The toggle for “Enable New/Edit Page Layout” will sync with the New/Edit Page Layout. Assignment Layout Settings follow Layouts or Roles. |
| Import Settings | Related APL code |
| Custom Role | Associated Feature Permissions, Field Permissions |
| Preset Role | Associated Feature Permissions, Field Permissions |
| Approval Process | Associated User Groups, APL code. Approver assignments copy all dimension details. |
| Business Process | Associated User Groups, APL code. Node assignees copy all dimension details. |
| Workflow | Associated User Groups, APL code. Node assignees copy all dimension details. |
| Pipeline | Associated User Groups, Fields. Node assignees copy all dimension details. |
-
An outbound change set cannot be edited, deleted, or cloned while it is being uploaded.
-
We recommend avoiding creating users or departments in a sandbox solely for packaging in change sets. IDs for newly created users and departments in a sandbox may not match IDs in production, which can cause unexpected results for metadata that includes user or department dimensions after deployment.
Delete an Outbound Change Set
Delete a specified outbound change set. Note: this operation is irreversible.
Clone an Outbound Change Set
Select an outbound change set as a template to clone. The new change set contains all metadata components from the source change set and its status will be Pending Upload.