- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 04:38 AM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 07:01 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 07:24 AM
Thanks Robbie
That sounds like the way to go, but certainly only in this special case.
/Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 07:24 AM
Thanks Robbie
That sounds like the way to go, but certainly only in this special case.
/Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 08:49 AM
No worries @Dan Gripping - I'm glad we could find a suitable solution.
Cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 05:18 AM
Referencing other companies? Doesn't really sound like a good developed application.
Just put them on 'ignore' so they will never be pushed and after the next clone they will be gone.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 05:36 AM
Mark Sanders, that is true, but never the less. 😁
The challenge is to set them as ignored, because that can only be done in the application scope, unless we bend the rules making them read-only, if possible. 😉
/Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 05:40 AM
If you can't set them to ignored, you also can't set them to completed, solving the issue as well. Your next clone will take care of them.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark