Not able change application scope.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-06-2017 01:40 PM
Hi,
I was working on SN application and for the testing purpose, I have installed it on another ven instance.But when I change the application scope and opened the record but it displays record is in application scope and you are in gloabl scope not in the application scope.Please refer the screenshot for reference:
RLCatalyst is my application and I have changed it from global to RLCatalyst.But still, when I open my record it displays the wrong message.Please help me out.I am not getting any idea what's wrong:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-17-2019 07:28 AM
I also have the same problem can anyone provide the solution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-27-2019 04:56 AM
As @toneking1989 has pointed out above, this occurs when the scoped application in question is missing a default update set.
To fix this quickly, select your application at the application dropdown at the top, and go to local updates sets using the ServiceNow navigator. Select the default(Global) update set, open it, and mark it as complete (make sure you create a backup by making another update set for global scope and merging the default set to it).
We need to ensure that the scoped application having the issue is selected when we mark the default (Global) update set as complete. This action will create a new default update set for global scope, and a default update set for your scoped application, and you should then be able to select your application and make changes to it, in an update set that is scoped for your application.
Thanks,
Rishabh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2019 04:35 PM
Thanks Rishabh, this solution worked for me
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-08-2019 09:30 PM
I'm glad it helped you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2020 09:37 AM
I'm also having this issue, seems like something that should be fixed in the platform? I'm not understanding the statement "this occurs when the scoped application in question is missing a default update set." If this is so critical, why is it broken? If this happens when you take an app to a different instance, how is this avoided in publication?
Like everything else with this platform, the topic of update sets seems massive and convoluted with no clear idea what it is and you have no awareness of it until you slam into it when it's not working. Any guidance demystifying this is appreciated.