moving update sets between instances

[asd22]

Hello.

I have about 6 update sets that we had in test that i "completed" and moved to our production instance before we updated test. I now wanna move them back from production to test again where they now don't exist. How do i do this?

[Anurag Tripathi · Accepted solution]

Hi,

Why do you want to move update set form prod to test?

In prod navigate to local update set and find them -> then you can export them in xml using the related link on each update set form -> then import update set in Tests or any instance.

But I don't understand why do you need to do so.

[Anurag Tripathi · Accepted solution]

Hi,

Why do you want to move update set form prod to test?

In prod navigate to local update set and find them -> then you can export them in xml using the related link on each update set form -> then import update set in Tests or any instance.

But I don't understand why do you need to do so.

[asd22]

I just got asked to do it by a senior, so im just doing it haha, but thanks

[raycallan · Accepted solution]

Hi asd22,

Assuming that you are doing an upgrade and were moving your update sets to prod to prevent them being overwritten as per Anurag best practice is to Export to XML, update your Test environment, the reload them using the Retrieved Update Sets -> Import Update Set From XML

If you are updating Test from a clone of Prod then the update sets should be copied across if you are using the latest backup

Either way you can use the same steps to copy the update sets from Prod to Test or alternately use the Update Sources and set u you Live Environment as the Source (3rd Screenshot)

[Pavankumar_1]

Hi @asd22 ,

how you moved update sets to prod?

After committing those update set will available on Local Update Sets >go to each the update set and use Export to XML option in related links.

or If you are trying to remove those customization which you moved through update sets then you have Back Out UI action on that completed update set.

But Back out is not the best practice to do.

If anything went wrong with these update sets, you can fix it by another update set then capture the correction in dev and move it to test and then prod. It is good approach.