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.
Data lookup does not work if the property glide.invalid_query.returns_no_rows is set to true - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Data lookup does not work if the property glide.invalid_query.returns_no_rows is set to true
KB0529866

Data lookup does not work if the property glide.invalid_query.returns_no_rows is set to true


2988 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Since the Calgary upgrade, data lookup is no longer working if the system property glide.invalid_query.returns_no_rows is set to true.

This is caused by the code that builds the Data Lookup cache. The code includes a query against the sys_class_name field, but that field does not exist on the dl_definition table and therefore the query returns nothing if the glide.invalid_query.returns_no_rows property is set to true.

You might see in the logs the following type of messages:

09/25/13 17:39:38 (135) D86C4A5D140C9900ED6FFD23809EEFF9 field name 'sys_class_name' not found in table 'dl_definition'
09/25/13 17:39:38 (137) D86C4A5D140C9900ED6FFD23809EEFF9 Loaded the Data Lookup cache in 2 ms
09/25/13 17:39:38 (329) D86C4A5D140C9900ED6FFD23809EEFF9 field name 'sys_class_name' not found in table 'dl_definition'
09/25/13 17:39:38 (331) D86C4A5D140C9900ED6FFD23809EEFF9 Loaded the Data Lookup cache in 2 ms
09/25/13 17:39:38 (517) D86C4A5D140C9900ED6FFD23809EEFF9 field name 'sys_class_name' not found in table 'dl_definition'
09/25/13 17:39:38 (518) D86C4A5D140C9900ED6FFD23809EEFF9 Loaded the Data Lookup cache in 1 ms

Steps to Reproduce

  1. Log on to an instance.
  2. Set the glide.invalid_query.returns_no_rows property to true (create it if necessary).
  3. Open the Incident > Create New module.
  4. Change the Impact or Urgency fields.

    Notice there is no change to the Priority field. In the base system, there is a Data Lookup Definition that should fire when the Impact or Urgency field is changed on an incident.

 

Workaround

This is expected behaviour. As a workaround, activate the Data Lookup and Record Matching Support for Service Catalog plugin, which is on by default for all new instances.

 


Related Problem: PRB590229

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.