Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Retrieved Update Sets don't Include any customer updates - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Retrieved Update Sets don't Include any customer updates
KB0787254

Retrieved Update Sets don't Include any customer updates


486 Views Last updated : Apr 16, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

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

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.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.