Global Default Update Set Override

[davidpanson]

Hi all,

I asked a similar question last week but now I've learned more about my problem. I have both the update set picker and application picker active on my Service Now instance. Whenever I pick an application with a global scope (therefore it should switch to global update sets) my instance will switch to a global update and then immediately switch to the last non global application I had selected.

This is what I'm talking about. In this case I had the SSH application selected in the application picker. Then I went to the global application selection in the application picker. The update set should automatically update to the new scope, and it does. It switched to Default[global] but then immediately switches back to the last application selected that was not global. In this case SSH.

I've tried it out on every other instance I have access to and only one of them is behaving this way. I can't replicate the issue on my personal dev instance. I have no idea why this is happening or what to do to fix it. Does anyone have any suggestions or similar experiences?

Thanks

[Mark_Bailey]

Hi David,

I applied a new integration update set (To DEV)   supplied by a vendor that creates a new application scope.

I now also have this issue where I can't create   a new update set under global.

I've also notice the default set still exist in local update set choices, but it is empty.

Before the application it had 11450 records on it, as seen on my TEST instance.

Did you ever find a solution for this?

[Mark_Bailey]

I did make a little progress. I see there are three Default on my DEV now.

The original and two created by new applications.

I can't figure out how to go back to the default application.

[Mark_Bailey]

Just resolved for me. It seems that the Admin role is really having some issues on Helsinki since I have it set as an elevated role.

I've noticed the admin role having issues on other things, so I set the role to NON elevated and all of the update sets show in my picker now.

On another Inc I had opened , ServiceNow suggested not using the elevated role for admin as it was causing some issues.

I've had it as elevated for three years, but Helsinki and elevated are not playing nice together.

[davidpanson]

That's good to know. My issue ended up being resolved by Service Now. I was not directly involved so I can't be specific with the resolution details. Apparently when I opened this thread my team had already opened a ticket with Service Now about this issue and had forgotten to tell me about the issue. They (ServiceNow) recommended using Chrome and not IE which did add some stability but did not fix the issue entirely. I thought the final resolution came from Service Now. Admin role issues do not surprise me one bit though. Glad you got everything sorted out.