Appearance
Change set FAQ
This article summarizes common issues when creating, uploading, validating, and deploying change sets.
WARNING
Supported component scope and error prompts require manual review.
Can a change set migrate business data?
No. A change set migrates metadata, not business data.
What is metadata?
Metadata is the configuration items in the enterprise management menu. Examples include objects, fields, layouts, permissions, flows, and custom functions.
What is the difference between outbound and inbound change sets?
| Type | Description |
|---|---|
| Outbound change set | A metadata collection sent from the current environment to an external related environment |
| Inbound change set | A metadata collection the current environment receives from an external related environment |
Can an uploaded outbound change set still be edited?
No. An uploaded outbound change set enters the Closed state. You cannot add or remove components.
Why does deploying a change set fail?
Common reasons include:
| Reason | Suggested action |
|---|---|
| Missing dependent components | Add the dependent components in the source environment and upload again |
| Conflicting configuration in the target environment | Check the target environment metadata |
| Insufficient user permission | Use an administrator account with deployment permission |
| Flow or script exception | Fix the configuration and validate again |
Can a change set delete metadata in the target environment?
Usually not. A change set adds or updates metadata. To delete metadata, handle it in the target environment management page.
Does a failed deployment keep part of the configuration?
The original manual states that when deployment fails, all content of this deployment rolls back. This rule requires manual review.