- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2023 10:09 AM - edited 03-31-2023 10:09 AM
Hello All,
Instance version(s): Utah and Tokyo
Problem began: Very recently (as of 2023-03-31)
I exported an update set from my packaging instance (venxxxxx) and tried to install it onto my development instance. It's been working flawlessly until today. Now all of a sudden all the files in the update set throws the "Failed to validate scope '<my_app_scope>' for update '<item>'" errors during the Preview Update Set stage. The Update Set Preview Problems tab is filled with the following error description:
"Cannot commit Update Set '<myapp>' because: Scope '<my_app_scope>' is not 'Global', not found in instance, but is found in app store. Install application from app store. Resolve the problem before committing."
Since this is a developer instance, installing from the app store is not possible. Has something changed recently to prohibit installing this way? How can I install my published app to my PDI for development/troubleshooting purposes?
Any help would be appreciated.
Thank you,
Jason
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2023 10:12 AM
I had this issue yesterday and simply just exported the application record (sys_app) to XML and imported it into the PDI and the problem was solved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2023 02:13 PM
I have the same issue that started Thursday and a newly build PDI. Difference is that it is not a published app, but just batched update sets from our development. When I import the xml batch file and try to preview, I get Cannot commit Update Set <name> because: Scope <scope> is not 'Global', not found in instance, but is found in app store. Any ideas? Did something change with ServiceNow and the PDI's?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2023 02:50 PM
If its a scoped app then you need the sys_app record from the instance that you developed it in. Just load that first and then your update sets. Or you maybe able to just include it in the update sets and have it work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2023 03:09 PM
The interesting part is that I was able to do this with no issues and like 5 hours later after a rebuild of my PDI, I am no longer able to. Does anyone know if something changed on the PDI's?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2023 08:03 AM
If you rebuilt the PDI then the sys_app record was removed and needed to be installed/put back.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2023 08:10 AM
Yes... that is exactly what I did.
1. I installed all of the needed plugins
2. I installed the update sets with NO issues
3. I wanted to retest this so I had my PDI rebuilt
4. I installed all of the needed plugins again
5. I tried to install the update sets but am getting the weird error.
I have done this process probably 50 times over the last 6 months and this is the first time I have ran into any issue. I have even tried to have my PDI rebuilt again and start over and have tried on a different version... No luck.