Cloning: Preserve Completed Global Update Sets

[mike555]

The ServiceNow Clone Profile page page has the option to "Preserve in Progress Global Update Sets" but it does not have the option to Preserve Completed Update Sets.

This can be done by excluding tables sys_update_set and sys_update_xml.

There would still need to be manual steps taken afterwards to re-apply the completed Update Set.

Is this likely why ServiceNow do have have this option on the Clone Profile menu?

[Bert_c1]

Hi,

the last I knew, that feature didn't work. you can set any In-progress update set to "Complete", and export those. then after the clone, import those and commit. If further development is needed on any, create 'version 2' and use the 'Batch' feature when promoting to other instances.

[mike555]

I know that.  My organisation has several staff doing work and it can be time consuming communicate and organize, to ensure all staff have exported their Dev Update Sets by the Clone date, whenever a clone is done.

[Dr Atul G- LNG]

Hi @mike555 

Greetings!!

Any specific reason to keep complete update set? If it is complete means its already promoted to next environment or my understanding is wrong.

Also, it is best to make in progress update set to close and take back up in XML format.

[mike555]

These would need to be kept when cloning down.

For example, I may have done work in an Update Set in Dev and marked it as complete.  Cloning into Dev would erase my work and the Update Set.