Save an update set for later

[Brent Cox]

On Monday, our system will be updated from San Diego to Utah. We have one update set that is very complex, but isn't ready to go into production yet. If I complete this update set and save the XML, can I then run a clone on PROD to DEV, upgrade DEV to Utah, and then apply the update set XML back to DEV without any issues? 

[Sandeep Rajput · Accepted solution]

Ideally you should be able to apply the updates by importing the update set XML back to your instance. Before doing the cloning exercise I recommend you to try importing the Update set XML on a sandbox and dev instance and see if you encounter any issues. Also, go through all the updates captured in your update set and see if something is missing. Changes in few records e.g. (Scheduled Job) are not captured inside update set and one has to use Add to update set UI Action to add them to the update set. 

[Brent Cox]

Perfect, thank you! This update set is exclusively for work flow items and variables in a catalog item. So all of this should be captured. I will import this XML into our TEST environment first to confirm no issues. As long as importing an XML update set from San Diego won't be an issue in Utah, then I think I should be good. 

[Sandeep Rajput]

Update sets are usually version agnostic (given that you are not trying to use an update set from Aspen/Berlin on a Utah instance as some of the features might have been deprecated a long time back). Since you are San Diego and Utah releases are just one release apart hence chance of any issues are slim to none.

[Brent Cox]

Thank you very much! This is my first time having to do this, so I wasn't sure if it would work or not. APpreciate the help on this.