Copy update set, keep only the records under my name

[lightblu]

Hi,

The issue I am having is that all my changes, as well as everyone else's changes, are captured in the "Default - Global" update set. This update set is huge, with thousands of updates. How do I clone the "Default - Global" update set and then only export/keep only the actions/records in the update set which were performed by me?

Also, how do I export an update set as XML? When I right click and export --> XML, it only exports the update set record, not all the things which were part of the update set.

My end goal is to export the Default - Global update set as an XML backup, but only the update entries which were performed by me.

Thanks for the help.

[lightblu]

What if I just wanted to manually put all the table records I created in an update set?

Manually because I want to choose which ones to keep, which ones to discard.

[Chuck Tomasi · Accepted solution]

Hi Lightblu,

You can do that. It's pretty much the same process. Use the update set list (sys_update_xml) to sort, filter, etc. and then list edit your way to set the Update Set field to what ever update set you want.

Personally, I like to create a new update set and put them there away from everything else so I know exactly what I'm getting. It's up to you.

[Pradeep Sharma]

Hi,

For those records which are required i.e customer updates move them to the newly created update set.

Please follow the instruction mentioned above for more info.

[Community Alums]

I created a Utility called "Copy Update Set" for this purpose.
see Copy Update Set - Share | ServiceNow Developers

This Utility allows users to copy "Update Sets" that have already been completed.  Users can then continue development on the next version of their code.

BENEFITS

1. The Utility adds a UI Action to the Update Set record (sys_update_set).  The UI Action is called "Copy Update Set".
2. This is useful for developers who want to restart work on an Update Set that they have already completed.
3. It is considered bad practice to re-open a completed Update Set i.e. change the status from "Completed" back to "In progress". 
4. The Utility uses OOP design patterns such as Unit Testing and Inheritance which you can copy and use for other projects.
5. The utility supports Updates Sets in different application scopes.
6. The utility supports parent/child Update Sets (i.e. batches).

[Nia McCash]

If you added everything to the default update set and need to move them to 'Chucks Update Set' in order to close and export, you can select multiple rows in the list of sys_update_xml entries by holding Shift + selecting the Update Set column with your mouse.   You should see multiple rows being highlighted like this:

And then when you double click on the first entry, you'll see that you can update all the rows at the same time to move them into a new update set, instead of having to move them one at a time: