In Salesforce, a change set is a collection of changes you want to move from one organization (usually a sandbox) to another (usually production). Below are the steps to create and deploy a change set from a sandbox to production.
Update Deployment Setting:
In Salesforce, Deployment Settings are typically managed to control which users or profiles have the ability to deploy metadata from a sandbox to a production environment using change sets. Managing deployment settings is crucial for maintaining the integrity and security of your Salesforce production environment.
Steps to Create Deployment Settings:
Login to Salesforce:
Login to your Salesforce instance, preferably as a System Administrator.
Navigate to Deployment Settings
In the Setup menu, enter “Deployment Settings” in the Quick Find box and select “Deployment Setting"
Add Deployment Connection:
Here you will see a list of available sandboxes and environments.
Locate the environment you wish to add and click "Edit" next to it.
Enable Deployment:
Check “Allow Inbound Changes” and save. This will allow you to deploy changes to this environment.
Confirm the Connection:
The other environment (usually a sandbox) will need to confirm the connection. Repeat the same steps as in 4 within the Sandbox Environment in Scope.
Log into the other environment, go to “Deployment Settings”, and you will see an "Outbound Connections" waiting for approval.
Click on the connection name and click “Accept”.
Verify Connection:
After accepting the connection, go back to the originating environment and verify under “Deployment Status” that the connection status is “Connected”.
Remember that the actual deployment of changes in Salesforce is typically done using Change Sets, Package Installations, Metadata API, or other deployment tools, and the Deployment Settings are just a part of controlling and managing the deployment process.
Once the Deployment Settings have been updated, the next step is to create a Change Set from Sandbox.
Creating a Change Set
Login to your Sandbox.
Go to your Salesforce sandbox where you have made the changes.
Navigate to Setup.
Click on “Setup” in the top right corner.
Create Outbound Change Set.
In the Quick Find box, type “Outbound Change Sets”.
Click “Outbound Change Sets”.
Click “New”.
Fill in the “Change Set Name” and optionally, the “Description”.
Click “Save”.
Add Components.
After saving the change set, you will see sections to add different types of components.
Click “Add” next to the component type you want to add.
Select the components you want to include and click “Add To Change Set”.
Add Profiles/Permission Sets (if needed).
You can also add profiles and permission sets, but this is optional and depends on your changes.
Profiles and Permission Sets need to be added separately in a special way to capture all related settings.
Upload.
Once you have added all components, click “Upload”.
Select your production environment as the target and click “Upload”.
This process may take some time, depending on the size of the change set.
Deploying a Change Set
Login to Production.
Once the upload is complete, login to your production Salesforce environment.
Navigate to Setup.
Click on “Setup” in the top right corner.
Access Inbound Change Set
In the Quick Find box, type “Inbound Change Sets”.
Click “Inbound Change Sets”.
Deploy.
You should see the change set you uploaded from your sandbox.
Click on the change set name.
Review the components and click “Deploy” to apply the changes to the production environment.
Monitor Deployment.
The deployment might take some time. Monitor the progress.
Once complete, validate that the changes have been applied correctly
Remember that deploying change sets can impact your production environment, so it’s best practice to do it during non-business hours and to thoroughly test all changes in a sandbox environment before deployment. Additionally, always have a rollback plan in case things do not go as expected after deployment.
Communicate the Change Set to Stakeholders
Create a Change Set
Verify with Stakeholders that all Metadata Components are included
Obtain Sign-off on Change Set
Promote it to Production
Validate first that the Change Set can Deploy
Instead of Clicking "Deploy," Click the "Validate" button
Communicate to Stakeholders when a change will occur
Often time after Business Hours
Promote the Change Set to Production
Click "Deploy" this time
Validate the Changes in Production
After the Change Set is in Production Run some Test Cases
Once Deployed, Check the Following:
Custom Fields:
If Deploying Custom Fields, make sure those fields are visible. Go to the Object in Scope > Fields & Relationships, Click on each Custom Field in Scope:
Click "Set Field-Level Security"
Select which Profiles it should be visible to
Custom Objects:
If Deploying a Custom Object, make sure that the Object is searchable or can be added to the User's App via a Tab.
Go to Set Up
Search Tab
Click New
Select Object
Give it a Tab Style
Select the Profile Visibility of the Tab - It can remain as Default On, if every Profile should have access to it. Click Next.
Select the Custom Apps that the Tab should belong to.
Click "Save"
Other Considerations:
Deployment Settings:
Permissions:
Ensure that users involved have the “Deploy Change Sets” permission if they are to deploy changes.
Profiles and Permission Sets:
It’s crucial to understand and carefully handle profiles and permission sets during deployment as they contain field-level security, object permissions, etc.
Test Classes:
When deploying code, make sure to include necessary test classes and ensure the code coverage is above the organization’s required percentage.
Backup:
Before deploying any significant changes, it’s prudent to take backups of data and metadata, especially in the production environment.
Deployment Windows:
Schedule your deployments during a window where it impacts the least amount of users if things go wrong.
Monitor Deployments:
After the deployment, monitor the system closely to ensure everything works as expected.
Check logs and run tests to verify the success of the deployment.