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.
Verifying that expected records are contained in the Update Set - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Verifying that expected records are contained in the Update Set
KB0535248

Verifying that expected records are contained in the Update Set


2334 Views Last updated : Sep 2, 2022 public Copy Permalink
KB Summary by Now Assist

Issue

  • There are instance issues post-commit
  • Update Sets show as committed but have inconsistencies
  • Not everything is updated after the update set completes

Cause

This issue can occur when an Update Set may be caused by a system error or warning, or unique key violation.

Resolution

Review the Update Set Preview for any errors, warnings, or collisions that may have been missed, or where unintended Skip actions were chosen.

If everything looks good in the preview, verify that the payload actually contains the updates that the customer is missing. If the updates are not in the payload, go to the Update Set source instance and review sys_update_xml.list for the missing records. If the updates are within the payload and have not been skipped, retrieve and review the Commit Logs:

  1. Locate and download the System Logs for the day that the Update Set was committed. You can do this by navigating to System Logs > Utilities > Log File Download.
  2. Once you have downloaded the System Log and opened it, use Find to search for lines that pertain to the name of the Update Set. Generally, the first lines you see are for the Update Set Preview, and following these are the Update Set Commit records. Review the commit records for anything out of the ordinary. This includes items such as: Warnings, Errors, Unique Key Violations, etc. 

If the logs show records for Unique Key Violations and/or Duplicate Entries and the Disposition within the Update Set Preview shows Insert when it should show Update, verify that the person committing the Update Set has their Domain in their User ID set to global. Having any other Domain listed causes the Disposition within the Update Set preview to be incorrect, and sporadically causes updates to be Inserted instead of Updated on commit-generating Unique Key Violations.

When using Domain Support, if the selected domain is anything other than global in the Domain Picker, the Commit UI action is removed from within Update Sets. 


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.