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.
"Uncaught TypeError: $j(...).popover is not a function" error thrown in browser console - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • "Uncaught TypeError: $j(...).popover is not a function" error thrown in browser console
KB0610282

"Uncaught TypeError: $j(...).popover is not a function" error thrown in browser console


10361 Views Last updated : Oct 17, 2023 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Description

The following error message appears in the browser console, which results in forms not loading correctly and potentially other issues based on where the error is received:
"Uncaught TypeError: $j(...).popover is not a function"

This may cause additional issues with loading related lists on the form, or with functionality of related lists when the error appears in the console.

Steps to Reproduce

Steps to reproduce are varied, but generally require creating and using non-platform standard jQuery includes.

Workaround

This is not a product defect.

It is generally caused by creation of global UI Scripts with conflicting versions of jQuery. When included in pages via making the UI Script global, or by including and calling the UI Script, the custom version of jQuery can conflict with the platform version of jQuery and overwrite functions necessary for base platform operation.

To prevent this error:

  • Utilize baseline jQuery functionality where possible and disable custom jQuery implementations.
  • Include custom jQuery libraries in a way that doesn't overwrite baseline functionality. As an example, use an identifier other than $j.
  • Contact professional services or trusted partners for implementation assistance.

Related Problem: PRB713498

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.