Deploying changes with change sets

In the previous section, we talked about the metadata changes that are deployed into a chain of sandboxes until the final production release.

There are different ways to achieve a metadata deployment:

• Metadata SOAP APIs (refer to https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_intro.htm for more information)
• The ANT Migration Tool (sometimes called the Force.com Migration tool—https://developer.salesforce.com/docs/atlas.en-us.218.0.daas.meta/daas/meta_development.htm)
• An IDE, such as Visual Studio Code (https://forcedotcom.github.io/salesforcedx-vscode/) or other popular IDEs
• Packages
• Change sets

Unlike change sets and packages, the other ways require you to master a developer's attitude. Let's start with change sets.

Change sets is a powerful feature that's meant to help administrators and...