The following KB details an issue when a user selects a scoped app in the application picker to find that the default update set is not reflecting the correct scope. The cause for this issue occurring is unknown but the issue is controlled at the user preference level.
The issue will usually manifest itself with specific users as the issue is not a global issue for all. To identify this do the following:
- Query sys_user_preference
- In your query look for all user preferences where name contains updateSetForScope. If you know the user that is seeing this behavior also add the query where user is the name of the user who is having the issue.
- In the result set if you did are not able to narrow down the user add the user field.
- Need to now obtain the sys_id of the sys_app record for the scoped application that is having the issue.
- go to sys_app > search for the name of the app > copy the sys_id
- In the result set from step 3 look for a record that has the sys_id of the scoped app that is having the issue (should look something like updateSetForScope0e9309a6139f76405d16b4622244b0d0
- In the value field of the record there will be another sys_id which should be the sys_id of the local update set for the default update set in the scoped application. If the sys_id is the sys_id of anything other than the sys_id of the local update set sys_id of the scoped application that you are in, here lies the issue.
- Delete the record(s) from sys_user_preference
- Clear the instance cache
- Log out/log back in as the users who were affected and now select the application picker for the scoped app that was having the issue. The default update set should now display properly in the right scope.
The value in this user preference is designed to point at the update set that has been most recently used