Moving multiple update sets to PROD

terp
Giga Contributor

Hi Community,

I'm looking for suggestions or thoughts on moving update sets to PROD.   (Cloning the environment isn't an option).   Our team built an app and has 10+ update sets in TEST, I need to move them to PROD.   Is it best to move the updates sets one by one? or merge them into one update set?

If I move them one by one, I'm concerned about the collisions AND identifying the order of the update set configurations.   Any thoughts after loaded, on how to identify the order I should commit the update sets?

What kind of issues have you run into when merging into 1 update set?

Thanks.

5 REPLIES 5

It is an awesome feature is you're certain the latest revision to any object is the authoritative one.