What are Change Sets?
One of the tools that Salesforce offers for transferring information changes between orgs is change sets. A method for synchronizing the metadata between a source org and a target org is provided.
Enterprise and Unlimited Edition environments enable change sets. Since it is a point-and-click application, no special software needs to be installed on your computer, nor do any files need to be downloaded or uploaded. Cloning change sets is a good approach to repeatedly construct packages within a project and certain layers of dependencies are examined.
What are the benefits of Change Sets?
The change set workflow, which many businesses start with at the center of their development process, is suitable for short changes and for smaller organizations:
- If non-developers need to implement changes, the graphical user interface (GUI) makes change sets accessible to a variety of people.
- It's simple to use and understand without adding any complicated processes.
- By using a few straightforward checkboxes, it is quick and easy to choose a small number of components to deploy.
- There is no extra charge for using change sets because they are part of the Salesforce membership price.
Don't forget to check out: Deploying Custom Field and Custom Object Through Change Set | Salesforce Developer Guide
Prerequisites for Deploying using Change Sets
- A connection between two organizations' deployment processes.
- The overall code coverage for the test class should be more than 75%.
- Create Change Sets and Upload it.
How does the Change Set work?
With the Salesforce UI, you can access this feature. The configuration of two organizations allows for the sending and receiving of modifications between them. These organizations must first be connected via a relationship to a common production instance, such as when creating a sandbox and development environment from the same production organization.
A list of modifications to be released is created by choosing components from the org and adding them to a change set. The UI in the source organization is used for this. The target org receives the change set when it has been built, at which point the changes can be accepted and implemented.
What are Outbound Change Set and Inbound Change Set?
Inbound Change Set: Change sets transmitted from the source organization to the destination organization are referred to as inbound change sets. For the changes to take effect, a change sent must be deployed. An inbound change set's contents can be deployed as a whole, but not component by component.
Outbound Change Set: An outbound change set is one that you want to deploy to the destination organization after creating it in the source organization.
The implementation of changes in another company is not always ensured by sending an outbound change set to that organization. Before the changes take effect, the target organization must deploy (accept) the change set.
Check out another amazing blog by Navdita here: All You Need to Know About Service Console in Salesforce
Deploy a Change Set
- From Setup, enter Outbound Change Sets in the Quick Find box, then select Outbound Change Sets.
- Click Upload next to the change set you want to upload.
- Then Go to another Organization and Find Inbound Change Set in Quick Find Box
- Next, Select the Change Set and Hit the Deploy Button.
- If you prefer to review the change set before deploying it, first click the name of the change set to view its detail page.