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.
Error Message: "Update scope id 'global' is different than update set scope id 'global'" When Attempting to Commit Update Set Preview - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Error Message: "Update scope id 'global' is different than update set scope id 'global'" When Attempting to Commit Update Set Preview
KB0819006

Error Message: "Update scope id 'global' is different than update set scope id 'global'" When Attempting to Commit Update Set Preview


11475 Views Last updated : Jul 11, 2023 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

When moving an update set from one instance to another via export XML getting the following preview error.

 "Cannot commit Update Set '<update_set_name>' because: Update scope id 'global' is different than update set scope id 'global'. Resolve the problem before committing."

 

Cause

The XML exported from the update set is missing the <application> element right below the XML element <sys_update_set action = "INSERT_OR_UPDATE>

Correct XML should look like 

<sys_update_set action = "INSERT_OR_UPDATE>

<application display_value="<application_name>"><sys_id></application>

Incorrect XML should look like

<sys_update_set action = "INSERT_OR_UPDATE>

 

This behavior is caused due to the below two ACLS on sys_package.name that are created by plugin com.glide.kmf.global which could have been installed when plugin Instance Data Replication (com.glide.idr) was installed.

https://<your-instance>.service-now.com/sys_security_acl.do?sys_id=c28ed511db230010ae05f4331f961911&sysparm_record_target=sys_security_acl&sysparm_record_row=5&sysparm_record_rows=6&sysparm_record_list=nameCONTAINSsys_package%5EORDERBYname

https://<your-instance>.service-now.com/sys_security_acl.do?sys_id=c28ed511db230010ae05f4331f961911&sysparm_record_target=sys_security_acl&sysparm_record_row=5&sysparm_record_rows=6&sysparm_record_list=nameCONTAINSsys_package%5EORDERBYname

 

Resolution

Add the roles required by the ACL to the user profile.

Roles required by the ACLs are

sn_kmf.cryptographic_manager
sn_kmf.cryptographic_auditor

Alternately, rather than add the roles to the admin role, set 'admin overrides' = true on the ACLs

  1. Elevate your admin role to security_admin.
  2. Navigate to each of these two read ACLs, one for sys_app and one for sys_package.name.
  3. Check the 'Admin overrides' checkbox and Click Save.

Related Links

Update set Preview problem - Cannot commit Update Set


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.