Best way to store update sets

[joshmorris]

We are cloning prod back to dev soon and I have an update set in dev that isnt ready to be promoted. What is the best way to store this update set until after the clone and re apply it?

[Dr Atul G- LNG · Accepted solution]

Hi @joshmorris 

https://www.servicenow.com/community/itsm-forum/preserve-update-sets-when-cloning/td-p/810249

Back it up!

Need to backup Update Sets before a clone? Simply whack all your in-progress update sets into a batch, complete, and export. This will give you peace of mind and works across multiple scopes (unlike the preserve update set functionality in clone profiles).

https://www.servicenow.com/community/developer-articles/everything-you-need-to-know-about-using-upda...

[kaushal_snow · Accepted solution]

Hi @joshmorris ,

The widely accepted and method I used in the past is:

Mark the update set as "Complete" in your Dev instance.

On the update set record, click the “Export to XML” related link to download it to your local system.

> Perform the clone (Prod to Dev).

After the clone, import the XML back into Dev via Retrieved Update Sets, then manually move it back to In Progress to resume work.

This approach ensures all changes in that update set are preserved and can be reapplied post-clone without interference.

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[Dr Atul G- LNG · Accepted solution]

Hi @joshmorris 

https://www.servicenow.com/community/itsm-forum/preserve-update-sets-when-cloning/td-p/810249

Back it up!

Need to backup Update Sets before a clone? Simply whack all your in-progress update sets into a batch, complete, and export. This will give you peace of mind and works across multiple scopes (unlike the preserve update set functionality in clone profiles).

https://www.servicenow.com/community/developer-articles/everything-you-need-to-know-about-using-upda...

[Dr Atul G- LNG]

https://www.servicenow.com/community/itsm-forum/how-can-i-save-in-process-update-sets-during-clone/m...

[kaushal_snow · Accepted solution]

Hi @joshmorris ,

The widely accepted and method I used in the past is:

Mark the update set as "Complete" in your Dev instance.

On the update set record, click the “Export to XML” related link to download it to your local system.

> Perform the clone (Prod to Dev).

After the clone, import the XML back into Dev via Retrieved Update Sets, then manually move it back to In Progress to resume work.

This approach ensures all changes in that update set are preserved and can be reapplied post-clone without interference.

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[Shashank_Jain · Accepted solution]

@joshmorris , 

There can be two ways :

1. The best way is to complete all your "In Progress" update sets and take the backup to XML using "Export to XML" related list. Once you clone the instance, import all your update set.

2. I do this sometime. The way that I do this is I open the Export to XML ui action, change the following fields:

Name: Export to XML (in progress)

Condition: current.state != 'complete

and then do an 'insert and stay'.   Now you're able to export your update sets w/o having to complete them first!