Upgrade Plan in DEV instance causing issues with other Update Sets in Global
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2023 02:17 PM
Hello everyone,
We have 3 instances, PRD, TEST and DEV.
In DEV, we enabled the Upgrade Plan in an attempt to help with future upgrades, but instead of helping, this is causing confusion with regular update sets in Global.
We worked in something in DEV, captured in a update set, marked as completed, exported the XML and then imported into TEST instance, when previewing it said many records were in different scope id and we noticed was the scope id for that Global Customizations - Upgrade Plan.
How to avoid this?
- Labels:
-
Service Catalog
-
Service Portal

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2024 01:56 PM
Nope, have not had any issues from moving the files back to Global. It didn't make sense to use to use Global Customizations scope since we never went ahead with the Upgrade Plan beyond our dev instance. That scope wasn't available to us in production so we had no choice, really.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2023 06:42 AM
Hi Nia, thanks a lot for the workaround. However, we don't still know why some of the updates are captured in Global Customizations - Upgrade Plan. Can we just delete this application as we decided not to use Upgrade Plan function anymore. It creates confusion and extra work: now, we need to check every time if some of the updates are captured in Global Customizations - Upgrade Plan and move them to Global because otherwise we cannot commit them on TEST due to two different scopes in one set.
Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2023 07:33 AM
I would think that once you've moved all the application files back to 'Global' scope, you should be able to delete the 'Global Customizations - Upgrade Plan' scope. Though, once you've moved all the application files back to the 'Global' scope, you shouldn't need to check every time if some updates are captured in the wrong scope and move them again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2023 08:07 AM
Hi Nia, I haven't tried what you said but understood why some updates appear in 'Global Customizations - Upgrade Plan' application. If you make an update that is captured also in "Customizations Unchanged" on the System Upgrade, that update will automatically move to 'Global Customizations - Upgrade Plan.'