Published at: 2026-09-17

04-create-an-outbound-change-set.md

After creating an outbound change set, you can package the metadata to publish.
[!WARNING] Supported component types, automatic dependency rules, and page paths require manual review.

Before you begin

  • You have permission to create change sets.
  • The target environment is related to the current environment.
  • The configuration to publish has passed testing in the current environment.
  • Prepare a component list for this release.

Step 1: Open the Outbound Change Sets page

  1. In the admin backend, go to Environment Management > Outbound Change Sets.
  2. On the Outbound Change Sets page, click New Change Set.
Outbound change set list and new entry

Step 2: Enter the change set information

  1. In Change Set Name, enter the release name.
  2. In Description, state the release scope and business impact.
  3. Click Save.

Step 3: Add metadata components

  1. On the change set detail page, click Add Components.
  2. On the Add Components page, select a component type.
  3. Select the components to include in the change set.
  4. Click Save.
The Add Components page displays all metadata components in your enterprise. You can select the metadata to include in the change set.
Add outbound change set components

Step 4: Check dependent components

  1. On the change set detail page, view the component list.
  2. Confirm the dependencies among objects, fields, layouts, permissions, and flows.
  3. If the target environment lacks a dependent component, add it to the change set.
[!TIP] When adding a field, confirm that the field’s object already exists in the target environment. If the target environment does not have the object, deployment may fail.
If the object of the field does not exist in the target deployment enterprise and the change set does not include the object, deploying the change set fails.

Expected results and validation

After an outbound change set is created successfully, its status is Pending Upload. Before upload, the metadata in the change set updates with the current environment’s configuration.

Common issues and troubleshooting

Issue Suggested action
Cannot find a component Check the component type and current environment configuration
Missing dependency during deployment Go back to the source environment and add the dependent component
A component should not be published Remove it from the change set before upload

Related resources

Submit Feedback
Previous
log-in-to-a-sandbox-environment
Next
05-upload-an-outbound-change-set.md