Published at: 2025-10-30
Outbound Change Sets
Outbound Change Sets
An outbound change set is a collection of metadata sent from the current environment to an externally connected environment.
1.1 Create an Outbound Change Set
Click the “New Change Set” button, enter a name for the outbound change set, and proceed to the change set details page. Click Add Components to include metadata components in the change set.
The Add Components page displays all metadata components available in your organization. Select the metadata you wish to include in the change set.
When adding components, consider whether their dependent components should also be included.
For example, when adding a custom field, verify if the related object to which the field belongs needs to be included in the change set.
If the object does not exist in the target deployment environment and the change set does not include it, the deployment will fail.
1.2 Upload an Outbound Change Set
After adding metadata components to the change set, you can upload it to the connected organization for deployment.
Click the Upload button on the list page or details page to initiate the upload process.
-
Before upload, the change set status is Pending Upload. Metadata in a pending change set updates dynamically with changes in the source environment.
> Example: If custom field A (text type, length 20) is added to an outbound change set, and its length is later modified to 30 before upload, the change set will reflect the updated length (30). -
After upload, the status changes to Closed. Metadata in a closed change set remains static and does not update with subsequent changes in the source environment.
> Example: If custom field A (text type, length 20) is uploaded and later modified to 30, the change set retains the original length (20). No components can be added or removed from a closed change set. -
When selecting certain component types, the system automatically bundles dependent components into the outbound change set. After upload, these dependencies appear in the component list.
-
Automatic dependency rules for change sets are as follows:
| Selected Component Type | Automatically Included Dependent Components |
|---|---|
| Object | Related import settings, layouts, validation rules, fields, Record Types |
| Field | Related APL code, global variables, picklists |
| Button | Related APL code, object mapping rules |
| Layout | Related APL code (UI events) New/edit page layout toggle syncs with new/edit page layouts Assignment layout settings sync with layouts or Roles |
| Import Settings | Related APL code |
| Custom Role | Related functional permissions, field-level permissions |
| Preset Role | Related functional permissions, field-level permissions |
| Approval Flow | Related user groups, APL code Node assignees copy all dimensional assignee information |
| Business Flow | Related user groups, APL code Node assignees copy all dimensional assignee information |
| Workflow | Related user groups, APL code Node assignees copy all dimensional assignee information |
| Pipeline | Related user groups, fields Node assignees copy all dimensional assignee information |
- An outbound change set cannot be edited, deleted, or copied during upload.
- Avoid creating users or Depts. in sandbox environments, as their IDs may mismatch with production environment IDs, leading to unexpected outcomes for metadata involving user/Dept. dimensions.
Delete an Outbound Change Set
Permanently delete a specified outbound change set. This action cannot be undone.
Copy an Outbound Change Set
Use an existing outbound change set as a template to create a new one. The copied change set includes all original metadata components and has a Pending Upload status.