Skip to main content

Promotion Model

Promoting a change means exporting it from the source environment as a dataset and importing that same dataset into the target — never re-building the change by hand in each org.

A change built and unit-tested in DEV is exported once as a dataset — records and metadata together, package.xml versioned as the scope contract — then imported into SIT, where the same dataset promotes onward; failures are fixed in DEV and re-exported, never patched in the target

Rules​

  1. One dataset per promotion. The export that goes to SIT is the export that goes to UAT. Do not re-export from a later state of DEV.
  2. package.xml is the scope contract. If it is not in the package.xml, it does not move. Review the package.xml as part of the change review.
  3. No manual configuration in target orgs. If something must exist in SIT, it must arrive there via an import.
  4. Failures are fixed at the source. If an import fails, fix in DEV, re-export, and re-import — do not patch the target directly.
Stub

Add the worked example with screenshots: exporting a real change from DEV and importing into SIT, including the result screens.