Missing Update Set [Needit Application]

[Ary1]

Hi, I'm facing an error where every time that I tried to switch to my applications scope it use the global scope.

I notice that my app was using the Default[Global] Update set, so I went to my Local Update Sets list and there was not Update Set for my aplication, however, there was an Update set with an empty Aplication, odd at least. 

I tried to create a new one, but since the application field is auto populate and read only (and I'm using the Default Global Update set), I can't change the 'Global' value, 

So.. My Application is from the learning path, so no big issue, but I'm certainly curious about how this happened, How can avoid it and how can resolve it.

Thanks!

[Sam Ogden]

Hi Yadin,

Thanks for the above.  How do you raise a support issue for a personal Dev instance?

Thanks

Sam

[Yadin]

Sorry not sure about that, this was for a VEN instance which is in the HI portal, not a DEV.

[Sam Ogden]

Hi,

I've come across the same issue, wondering if you managed to resolve it?

Thanks

Sam

[Trevor Muhl]

Hello,

I encountered this issue (a missing "Default" update set) and managed to find a way to resolve it. This solution requires that you have the application installed on a separate instance.

1. Open the "Default" update set for your application on a separate instance.
2. Export the update set record to XML using menu > Export > XML (This Record). Do not use the related link action for this step.
3. Import that update set into the affected instance. At this point, switching to the application scope still does not automatically select the imported update set.
4. Open the imported update set.
5. Make sure you have the correct application scope selected. Then, make a duplicate of the update set using menu > Insert and Stay.

Once completed, switching application scopes will properly apply and will also automatically select the new "Default" update set for your application.

Let me know if this is helpful!

[sal7]

The issue may be caused by PRB1395849

When a user selects a scoped app in the application picker, the update set points to the default update set, which does not reflect the correct scope.
The result is
-- a user cannot create a new record for his application, or work on the application because the system keeps switching the scope to Global.
-- a user commits to his git repo, but Studio still thinks there are local changes that haven't been committed because the update set points to the Default update set instead of the application's update set.

This KB page describes the issue and the fix:
KB0793433 - Default update set in scoped app is showing default set that is in application global from update set picker

https://hi.service-now.com/nav_to.do?uri=%2Fkb_view.do%3Fsysparm_article%3DKB0793433