I’ve spent this past weekend in change set hell. I have 4 change sets that have to be deployed, with each one dependent on the next. Everything is documented in a super detailed deploy book but still the first one, the easy one failed. And then failed again. And again. Change sets are definitely one of the Circles of Hell from Dante’s Inferno. So how can you make change sets less painful?
- My first tip for change sets came to me a couple of years ago and it certainly has helped with the creation of change sets. ORGanizer, a Chrome extension, has a Change Set plugin. This has a better way to add and remove components and you can even make templates with it. If you are creating change sets with lots of pieces, this is an admin’s best friend. I’ve heard rumor that there is an even more awesoem
- tool called Salesforce Change Set helper. Unfortunately I have never been able to get that to work on my work laptop… so when I get a spare moment (haha like that happens) I will have to try that on my personal laptop, cause everyone moves change sets for fun.
- Know how to find known issues. In change set one, I encountered not one but two known issues. I was getting unexplained errors on validating the change set. Both were finally explained with a trip to the Salesforce Known Issue page. Head on over here to find out if you might be running into one of the Known Issues and see what the steps are to mitigate it.
- Don’t delete old versions of change sets until you are good to go. Instead, make sure you give them a version number so you can track them. One thing that happened during these deployments was someone accidentally clicked delete before cloning the change set. Since this individual did not like use this method of saving old versions, there was nothing to do but start over. This wasted a good 2-3 hours while I went back through the deploy book and recreated our change set. I prefer to send one, if it fails, then clone and rename it v2 and so forth.
- Finally, keep a neat and organized deploy book. You may encounter problems even with a full list of everything you need to deploy but this will help. It is also helpful to look through the dependencies that Salesforce identifies. Often it lists ones that you do not need to include because they already exist in the next environment, but its helpful to flip through it because there may be a few diamonds in the rough.
What are your favorite tips for when you have the change set blues?