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.

[Chuck Tomasi]

Hi lightblu,

My recommendation is to go to the sys_update_xml table and set the Update set reference field to point to the right update set. Don't worry about copying or exporting the default global. You can sort by who created or updated various records and start sorting them in to their respective update sets simply by modifying the value of that field.

When you get it all done, mark the update set as complete and then you can use the Export To XML UI action (not the right click Export XML menu option)

[Chuck Tomasi]

Pictures for reference:

Go here

Modify the Update Set Field

Go to the update set record and mark complete & Save

Use Export to XML here.

[lightblu]

Hi Chuck,

I get what you are saying, but it's very painful for me to through every record in that table and change the update set to the one I want. I guess I could write a script.

Is there an easier way to just back up all the records you created? Perhaps manually adding all the records I created to a new update set?

I am supposed to back up all my ServiceNow work in my dev sandbox because we are cloning a prod instance onto my dev sandbox. Is backing up all the records I created to an XML file the best way to do this? We cannot clone the dev sandbox to another environment because we have no more environments.

[Chuck Tomasi]

I would recommend against exporting the global default update set. Once you close it, it's going to create a new one "default 1", if I recall.

Putting ALL the changes from the default update set may not be wise. I recommend going through the entries and review them, then modify them as needed.

Perhaps if the "unwanted" changes are few, you can move those to an UNWANTED update set, then write a script to move everything else to the update set(s) you want. That may be a smarter approach.