When the Default Update Set is needed

d-aizawa · ‎05-12-2022

Hi.

I have been using ServiceNow for the first time in almost a year.

Let me ask you a question about Update Set.

I was told to move to the default UpdateSet instead of deleting the unnecessary Updates recorded in the UpdateSet.

But when do you need the Update record you thought you didn't need again?

Is there a case where you have a problem by deleting the Update of UpdateSet?

Thank you!

Community Alums · ‎05-12-2022

Hi @d-aizawa ,

I believe you lose the record of the changes, but not the changes themselves. So if you made some changes to a form in an update set, you delete that update set, the changes remain, but the history of those changes contained in the update set will go away.

Normally, you don't want to delete update sets... you want those records of changes in the system in case they are ever needed to bail you out of trouble. If you don't want these things applied, you could move then to a different update set and set it to ignore, rather than delete those records. The caveat there is that if you made multiple changes to the same field, it only records the most recent state so if you move the latest update of 4 made, it's removing all updates to that record.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

View solution in original post

d-aizawa · ‎05-12-2022

Thank you for answering the question.

I would like to know why unnecessary updates should not be deleted.

Thank you!

Aishwarya Thaku · ‎05-12-2022

Hi @d-aizawa ,

If you delete the entry from the update set, there is a risk if you delete something that is getting referenced in your implementation or if there is any dependency on it.

It is your personal preference to delete it or move it to default. However, I would recommend you to move it to default as you can recover anything if you deploy it to another instance and if the functionality breaks.

Please mark it as correct or helpful if it helped you in any way.

Thanks,

Aishwarya