Is there a proper way to back-up unfinished update sets?

[Anastasia Ty-Ch]

Hi everyone!

We are planning to upgrade to UTAH version however, we still have some unfinished update sets. May I ask if there is a proper way to back-up those update sets? What I did was, I set the update sets to COMPLETE and at the RELATED LINKS, I clicked the EXPORT TO XML. I downloaded the XML files and import it to the upgraded instance.

But when I checked if all my previous work from the unfinished update sets was transferred to the UTAH version, it wasn't there. I might have missed something or probably didn't back-up the update sets properly. 

Please let me know if there is a correct way to do it. Thank you

[jMarshal]

You're doing it correctly...but make sure you go to "Retrieved Update Sets" to import the XML file (related link on that page), not just "Load Data":

If your development is still missing, I would suspect it was in a different update set than the one you exported (default set perhaps?).

[Anastasia Ty-Ch]

Hi @jMarshal thanks for responding. I'll check this step and will let you know if it works.

[Harshal Aditya]

Hi @Anastasia Ty-Ch ,

Hope you are doing well.

After importing the update set , may I know if you have retrieved and committed the update set.

Navigate to local update set ,search for your update set and check if it is committed or not.

If not you need to retrieve and then commit 

Also additionally you can explore batching of update set option as well.

Regards,

Harshal 

[Anastasia Ty-Ch]

Hi @Harshal Aditya, thank you for responding. I'll take a look at this and will let you know if this works.