how to delete a scoped application update set, when application is no longer installed

[Dan Gripping]

We have had an application installed which is not available anymore. There is still update sets referencing to the application on the instance with references to other companies, which should be removed. 

But, how can we delete the update set, when we can't select the application.

[Robbie · Accepted solution]

Hi @Dan Gripping,

This does seem like an odd situation. There is a workaround where we can remove the company name which I'll outline below. This update works regardless of scope access etc. 

For others reading this on the community, only follow these steps in exceptional circumstances similar to what @Dan Gripping has outlined.

- Navigate and open the update set which we would like to rename

- Right-click in the update form head and select 'Export' and then 'XML (This Record')

- Open the downloaded XML file in a suitable editor and find the XML stage labeled '<name>'. It is here where you can remove the name of the company or rename as you see fit

- Save the XML file change

- Back in ServiceNow, Navigate back to the list view of all update sets. 

- When hovering your mouse over one of the column headers of the list view such as the 'Name' column, right-click and select the 'Import XML' option. 

- Select the XML file that you've just downloaded and edited. Once the file is uploaded, you'll see the update set will now reflect the name change.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie

[Community Alums]

Hi @Dan Gripping ,

Deleting an update set is a bad practice. To revert a customization, back out the update set rather than deleting it.

Administrators can delete an update set only when it is not the current update set and it is empty (no sys_update_xml entries are associated with it). For example, after merging update sets, you might want to delete the original sets. This function is restricted by an access control rule (ACL) on the Update Set [sys_update_set] table.

ServiceNow strongly recommends that you do not delete sys_update_xml entries, because this action:

• Does not undo the updates.
• Removes any record of who applied the customizations.
• Removes the sys_update_xml entries associated with the update set, so customizations are overwritten when the instance is upgraded.

When you try to delete an update entry, a warning message appears. Click OK to confirm the deletion.

[Robbie]

Hi @Dan Gripping,

Can I ask as to why you want to delete the update sets and what harm or effect they are causing you/your instance?

You'll notice, baseline configuration there is no Out Of The Box option to delete an update set - and this is for good reason - it is not recommended at all and could actually affect the instance itself by affecting not only the application you refer to, but also potentially other related apps/functionality depending on what's been implemented and how.

The recommended best practice would be to set any update set(s) to the state of 'Ignore' in the lower environments and not delete the update set or any related sys_update_xml entries.

Whilst I recognise you do not see or use the app, understanding what has been applied to your instance and when is important when debugging issues or implementing/configuring changes moving forward.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie

[Dan Gripping]

Sure Robbie, 

The reason is that we are using MSP instance, where we copied the customer Domain from our instance to an new instance. We used a tool from ServiceNow to do this. 

But the update sets from the applications( which was not copied the new instance), was copied to the new instance. The records in the update set, is not referring to anything, but the name of the update sets, are referring to other companies. That is why we need to remove them or rename, but either of this we can not do.

[Robbie · Accepted solution]

Hi @Dan Gripping,

This does seem like an odd situation. There is a workaround where we can remove the company name which I'll outline below. This update works regardless of scope access etc. 

For others reading this on the community, only follow these steps in exceptional circumstances similar to what @Dan Gripping has outlined.

- Navigate and open the update set which we would like to rename

- Right-click in the update form head and select 'Export' and then 'XML (This Record')

- Open the downloaded XML file in a suitable editor and find the XML stage labeled '<name>'. It is here where you can remove the name of the company or rename as you see fit

- Save the XML file change

- Back in ServiceNow, Navigate back to the list view of all update sets. 

- When hovering your mouse over one of the column headers of the list view such as the 'Name' column, right-click and select the 'Import XML' option. 

- Select the XML file that you've just downloaded and edited. Once the file is uploaded, you'll see the update set will now reflect the name change.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie