Understanding the limitations of Salesforce Change Sets
Change Sets arrived in 2010 and have been the native, low-code way to move metadata between connected Salesforce environments ever since. The functionality has barely moved, while Salesforce DevOps practice has. A Change Set only deploys metadata between orgs connected to the same production instance, and it has no native integration with source control, which rules it out of a modern CI/CD pipeline.
The bigger gap is record data. Change Sets cannot deploy an Account or an Opportunity. Once uploaded they go read-only, so any mistake means starting again. Selecting components by hand, working out the dependencies, and making sure they all made it in is slow, error prone work, and it shows in the user experience.
Introducing DX Inspector, a modern deployment option
Salesforce is addressing those limits with DX Inspector, an expansion of DevOps Center that handles both configuration metadata and record data.
Unlike Change Sets, DX Inspector connects directly to a wider range of environments: sandboxes, scratch orgs, developer orgs, and production orgs.
Key features and benefits of DX Inspector
- Environment flexibility. It connects straight to the various Salesforce org types, so the deployment scope is wider.
- Source control integration. It optionally works with DevOps Center, so changes get versioned, collaboration happens through pull requests, and you get an audit trail that fits modern DevOps practice.
- Metadata and record data deployment. Both configuration and data deploy natively, with no supplementary tools.
- Advanced dependency management. It handles metadata dependencies up to 50 levels deep and data dependencies up to 10 levels deep. For data migrations, set up External ID fields in advance and plan the migration in dependency order.
- Deployment flexibility. You can change the deployment package right up until you hit 'Deploy'.
- Automated change tracking. It uses Source Tracking (available in Developer Sandboxes, Developer Pro Sandboxes, and Scratch Orgs) to track and consolidate changes into a single view, which cuts the manual documentation overhead.
Note: not every Salesforce component supports Source Tracking yet. Keep your own deployment checklist so nothing goes missing, and check the Metadata Coverage Report for what is supported.
DX Inspector vs. Change Sets: a comparison
| Feature | Change Sets | DX Inspector |
|---|---|---|
| Can Deploy | Metadata | Metadata and Record Data |
| Tracks Changes? | No | Yes |
| Dependency Mgmt? | Yes | Yes |
| Is Flexible? | No, read-only once uploaded | Yes, editable up to 'Deploy' |
| Source Control? | No | Yes, with DevOps Center |
| Environments? | Tied to the same Production org | Sandboxes, Scratch Orgs, Developer Orgs, and Production Orgs |
| Metadata Support | See Metadata Coverage Report | See Metadata Coverage Report |
Conclusion
DX Inspector is a real step up in Salesforce deployment tooling. If you already work in source control and CI/CD, it slots in through DevOps Center. If you are still on Change Sets, it takes away most of what makes them painful and should make deployments smoother.
Leave a Comment