What are the DELETE entries in my update_set and do I need them?

[spike]

When I create an update set, and then make some changes as I go through the development process, I get lots of entries in my update set that say DELETE.

I'm assuming it's deleting database entries (when it's not something new) and then INSERT_OR_UPDATE-ing my changes.

And that makes sense.

However my production admins have told me that I should move all of the DELETE entries from my update set to the Default set. To me this means the deletes aren't needed, which makes me question why ServiceNow would create them in the first place.

Does anyone have any thoughts here? Should I be deleting these? Are my admins correct? Or should we be doing something else?

Thanks for any advice.

[Kalyani Jangam1]

Hi,

Ex you have one requirement in which you initially think this will be solve by using Ui policy so you create the UI policy and now you understand that this will not achieve using Ui policy but solve by using client script so you make your UI policy deactivate and create new Client script. Your requirement fulfilled using client script and why keep unnecessary deactivate UI policy in instance then you delete this Ui policy. Once when we move the update set and keep deleted entry of Ui policy then unnecessary Ui policy record created in new instance and deleted also.

Hence your admin is right we generally move deleted entry in default update set so that it will not move to the next instance because there is no purpose.

[Ankur Bawiskar]

Hi,

One good example would be

1) Consider you have created a business rule which you are no longer willing to use but that has already been promoted to production

2) you can either inactivate that or delete that and capture in an update set

3) this will help during migration so that the component gets deleted in the next instance where it will be migrated

Regards
Ankur