LEARN. PRACTICE. GROW.Concept and mechanism
The test environment should match the evidence needed. Developer and Developer Pro provide configuration without an automatic complete copy of business data. Partial Copy combines metadata with a template-defined sample; Full provides greater data fidelity under its own copying and refresh conditions. A sample is not automatically anonymous, and a sandbox may still require external-integration review. Choose an environment by test type, volume, dependencies, and authorized data. Before a change set, list components and relationships: including a custom object does not guarantee sending every field, and some flow references require manual inclusion.
Guided application
Change sets do not perform component delete or rename. Retiring old elements requires an explicit plan for consumers and target. A flow version present at the target still needs confirmation of state and activation settings. Also separate metadata from business records the application needs: load reference data after compatible schema exists, validate identities, and reconcile outcomes. Customized unmanaged packages must not be treated as supporting managed push upgrades; preserve differences before updating or reinstalling. Final acceptance includes functional tests, support responsibilities, follow-up steps, and agreed recovery. A green technical status alone does not establish that the application contains the data and behavior required by the business.
A release sends an object and flow but omits fields, an approval process, and reference data. The team completes dependencies, validates at the target, confirms activation, and loads records with reconciliation. Each step has an owner and completion criteria.
Common pitfalls
Object treated as every field; change set treated as business data; validation treated as activation; unmanaged treated as automatic upgrade; sample treated as anonymization.
Related topics: Requirements, access, and platform extensions · Relationships, lifecycle, and reporting · Fields, migrations, and external data
Sequence metadata, data, and activation. Accept the complete operation with known dependencies and recovery.
Reference: Change Sets Best Practices · Platform App Builder guide SU 26