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.
Console error on change record having conflict detection - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Console error on change record having conflict detection
KB0860205

Console error on change record having conflict detection


337 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Steps to reproduce:
1. Open any change request record having conflict detected.
2. Go to the inspect element and click on the console.
3. An error with the red mark will come saying.
"Uncaught TypeError: Cannot read property 'hide' of null
at updateWarningBoxAndConflictButton (ChangeRequestConflictUtils.jsdbx?v=08-10-2020_1624&c=31_853:190)"

Cause

The issue is occurring as the Ui marco "change_request_conflict_progress" was customized.

Resolution

// Get references to the two gui widgets you intend to enable/disable
var warningBox = $('conflictDetectionStatus');
var checkConflictsButton = $('conflict_action_run');
<div id="conflictDetectionStatus" class="outputmsg outputmsg_warning notification notification-warning" style="display: none">

The Ui script : ChangeRequestConflictUtils was calling function updateWarningBoxAndConflictButton
Where it was fetching conflictDetectionStatus parameter from the above Ui macro which was returning null causing the error in the console.

Reverting the same to OOB, resolved the issue


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.