Notifications

3 views

Description

When retrieving an update set from another instance, the update set doesn't include any of the customer updates that are seen in the update set on the source instance.

Release or Environment

Any

Cause

-- This is mostly likely caused by the Authorized User in the "Update Source" record for the source instance, not having the admin role. 

-- Another cause could be that the authorized user DOES have the admin role, but the admin role has been set up as an 'Elevated Role', which basically renders the admin role unusable.

Resolution

1. On the instance where you want to commit the update set, navigate to System Update Sets > Update Sources and open the update source record of the instance you are retrieving the update set from.

2. Note what username is set in the record.

3. On the source instance, navigate to User Administration > Users and find the user record of this user, and confirm they have the 'admin' role assigned. If they don't have the admin role then assign it to them, OR change the user to one that does have the admin role.

4. If the user does have the admin role assigned, then click on the admin role from within the user's record and confirm the 'Elevated Role' checkbox is not checked. If it is checked, you will need to uncheck it for the user to actually be able to do any of the admin functions. This is because when a role is set to be an elevated role, then user's with the role have to "elevate privileges" in order to be able to use the role, but in order to elevate privileges, you must have the admin role. Therefore, if the admin role is set as an elevated role, it essentially breaks the admin role.

Article Information

Last Updated:2019-11-26 11:53:16
Published:2019-11-26