Salesforce Winter '27 adds Omnistudio Clean Metadata Deployment, letting teams deploy Omnistudio components alongside Apex, LWC, and flows in one metadata pipeline.
Deployment tools and metadata
Clean Metadata Deployment supports Salesforce CLI, change sets, and 1GP/2GP packages. Supported metadata types include:
- OmniUiCard
- OmniScript
- OmniIntegrationProcedure
- OmniDataTransform
The feature provides atomic deployment, automatic dependency detection, single-version management, readable diffs, sandbox copy, and source tracking.
Enable Clean Metadata Deployment and test in a sandbox
The feature is available on the **standard runtime and designer**. Managed-package users must migrate before adopting it.
Turn on **Clean Metadata Deployment** in **Omnistudio Settings** in both the source and target orgs.
The following sandbox checks are editorial recommendations, not Salesforce requirements. Select the Omnistudio components to test and choose a supported deployment route.
- **Test a successful combined deployment.** Deploy the selected Omnistudio components with their dependencies alongside the intended Apex, LWC, and flow components. Check that dependency detection identifies the expected dependencies and that the combined deployment succeeds.
- **Test atomic deployment with a known failure.** Record the selected components’ pre-deployment state, then introduce a known failure into the combined sandbox deployment. After it fails, compare the components’ state with the recorded baseline. The check passes only if no partial changes remain. Include the failure response and the before/after comparison in the test results.
Record expected versus observed results for both checks.