I have retrieved an update set twice from Dev to QA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2017 09:26 AM
I have retrieved an update set twice from Dev to QA, one through remote instance and the second through retrieved update sets -> export XML. So basically now in my QA instance, i have duplicate update set. My question is can i delete one of them?? Or if i commit both of them would that create any conflict??
Please help me out ASAP what steps do i need to do. I have to complete this in QA by EOD.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-13-2017 07:35 AM
In that case merging is the only option. You can try merging update sets in DEV & the commit it in QA. Before committing merged update set in QA you need to roll out or back out the update set that was committed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-21-2017 08:09 AM
Hi Jaspal,
What affects will changing the name of a servicenow group in an organization have on metrics, SLAs etc.?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2017 09:31 AM
You can go to retrieved update sets and delete the update sets from there.
If you were to commit both and it created a conflict (which most likely it will when previewing) you can always roll back the update sets in the update set menu. I have done this before and I personally just deleted the duplicate.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2017 10:28 AM
Hi,
I would rather recommend to get it sorted by created (Z-A) & then commit the one that is latest of the two. As deleting anything at any point does not seems to be in line with ServiceNow's Best Practice.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2017 10:30 AM
I can agree with that, in the past if I have a duplicate update set I have previewed one and it came back with errors about "cannot find referenced item but did find it in an uncommitted update set" I could see on the one I previewed where the creation of the item was. when I deleted the duplicate the issue would go away and things worked without any further issues.