Migrating update sets between different family versions

[Pat Surtan]

My Dev is currently in Tokyo but Test and Prod are still in San Diego.

I have my update sets backed up via xml from Dev before the Tokyo upgrade.

What is the best practice in migrating my Dev update sets to Test and Prod now that they're on different family releases? Is it okay to just promote my update sets to Test and Prod? Or should I import my update sets into Test and Prod while they are still in San Diego, commit them; then upgrade Test and Prod to TOkyo?

[SanjivMeher · Accepted solution]

Depends on what you have in your update set. 

If there is nothing important which you think may not impact due to upgrade, you can move them to Test and Prod. 

Best practice is to upgrade Prod and Test and then deploy the dev update set. But if there is an urgency to deploy, as a developer, you should be able to identify if there is an impact even if you migrate update set with different family version.

[ersureshbe]

If system OOB updateset part of Tokyo it will create an issue. Not sure what's present in the update set XML we can't comment there.

If you and your team created update set and captured something (Dev instance) then it will not create an issue. But one condition, you should check the form functionality and behaviour both are same.