Tag Archives: ChangeSets

Limitations of Salesforce ChangeSets

ChangeSets is one of the tools that Salesforce provides for developers to migrating metadata and configuration changes between environments. There are some limitation in ChangeSets. Here are the limitations of ChangeSets, that is why developers need alternative deployment solutions to ChangeSets.

  • You cannot deploy all types of metadata components in one shot. For example, if you are deploying custom settings and a Visualforce page which leverages those custom settings, we cannot deploy all those components at once. Developers would first need to deploy custom settings, and then create a Changeset for deploying Visualforce page.
  • Code merging from various organizations into a single deployment unit is not feasible by using Salesforce ChangeSets. Salesforce recommends that each developer work in their own developer organization.
  • You need to create Salesforce ChangeSets over and over again. For example, if a developer needs to deploy the code from Dev to QA to UAT organizations, they would have to create the ChangeSets twice to move across these two organizations.
  • There is no way to deploy successful components and ignore the failed components. Salesforce ChangeSets either deploy all the components or rollback all the components on any failure.
  • Salesforce ChangeSets do not support all types of metadata components.
  • It’s not feasible to integrate Salesforce ChangeSets with any version control system.
  • Stop overwriting changes from other developers, because metadata components are not versioned, we often overwrite each other’s changes. For example, a developer can deploy the latest version of a component. Subsequently, another developer can redeploy the “older version” of the component which was not changed.
  • For any deployment, developer need to upload ChangeSets and deploy them to the target organization. This greatly increases the deployment time.
  • Any developer can make any modification to another organization if they have permissions to make changes to it. The auditor cannot track who made the changes to the organization.