+ Start a Discussion

Best practice for large change sets

I was wondering what peoples views were on big deployments when you have hundreds of components of various types.

I have seen developers build one huge change set which includes everything, so hundreds of components including Apex code, sharing rules, custom objects, process flows etc.

I have also seen developers break this down into smaller more manageable change sets, deployed in a strategic order. For example, the first changes set would include the custom objects and fields, so the data model is deployed. The second change set the Apex code and flows etc. A third changes set for sharing rules, permission sets etc. A fourth change set including page layouts, Lightning Pages.

What are peoples views on this, is it just preference, does one method make it easier to deploy?
ANUTEJANUTEJ (Salesforce Developers) 
Hi Simmo,

As mentioned in the link-https://help.salesforce.com/articleView?id=changesets_best_practices.htm&type=5 it is important that in case if you are deploying as parts you should do in a way such that the dependent components are deployed at a time.

Additionally, you could use this link [https://salesforce.stackexchange.com/questions/12272/what-is-the-most-effective-way-of-creating-a-change-set] that indicates about various ways you could deploy using an effective way for a large change set deployment.

I hope this helps in understanding the change sets best practices.