Notifications

24 views

Description

Dependency View Map, Map Settings, not showing Dropdown values of Dependency Types, if glide.invalid_query.returns_no_rows=true

Nothing is listed. You would expect values from all the Active records in table "ngbsm_script" to be listed.
Without that system property, they are listed.

All out-of-box code should work with that property set.

Steps to Reproduce

 

  1. Set system property glide.invalid_query.returns_no_rows=true
  2. Turn on SQL/Log session debug
  3. Open the Dependency View Map ( /$ngbsm.do )
  4. Click Map settings (the icon in top-right)
  5. Expand the Dependency Type drop-down 

Nothing is listed. You would expect values from all the Active records in table "ngbsm_script" to be listed:
\ngbsm_script_list.do?sysparm_query=active=true

Session debug (log/SQL) shows:

Working, without glide.invalid_query.returns_no_rows=true:

08:57:07.804: #16244 /api/now/table/ngbsm_script Parameters ------------------------- sysparm_fields=sys_id,name sysparm_query=ORDERBYname^user=david.piper@snc^active=true api=api 
log08:57:07.804: *** Start #16244 /api/now/table/ngbsm_script, user: david.piper@snc 
SQL08:57:07.806: Optimized away unnecessary join to [sys_metadata] for aggregate query against [ngbsm_script] 
SQL08:57:07.807: Time: 0:00:00.000 for: <instance>_1[glide.22] SELECT ... FROM ngbsm_script ngbsm_script0 WHERE ngbsm_script0.`active` = 1 /*...*/ 
SQL08:57:07.810: Time: 0:00:00.001 for: <instance>_1[glide.22] SELECT ... FROM (ngbsm_script ngbsm_script0 INNER JOIN sys_metadata sys_metadata0 ON ngbsm_script0.`sys_id` = sys_metadata0.`sys_id` ) WHERE ngbsm_script0.`active` = 1 ORDER BY ngbsm_script0.`name` limit 0,10000 /*...*/ 
log08:57:07.815: *** End #16244 /api/now/table/ngbsm_script, user: david.piper@snc, total time: 0:00:01.243, processing time: 0:00:00.022, total wait: 0:00:01.221, session wait: 0:00:01.220, semaphore wait: 0:00:00.001, SQL time: 0:00:00.001 (count: 5), ACL time: 0:00:00.001, source: 199.91.137.60 , type:rest, method:GET, api_name:now/table, resource:now/table/ngbsm_script, version:Default, user_id:david.piper@snc, response_status:200 

Broken, with glide.invalid_query.returns_no_rows=true:

09:10:14.690: #16416 /api/now/table/ngbsm_script Parameters ------------------------- sysparm_fields=sys_id,name sysparm_query=ORDERBYname^user=david.piper@snc^active=true api=api 
log09:10:14.691: *** Start #16416 /api/now/table/ngbsm_script, user: david.piper@snc
SQL09:10:14.692: Optimized away unnecessary join to [sys_metadata] for aggregate query against [ngbsm_script]
SQL09:10:14.694: Time: 0:00:00.001 for: <instance>_1[glide.21] SELECT ... FROM ngbsm_script ngbsm_script0 WHERE 0 = 1 AND ngbsm_script0.`active` = 1 /*...*/
log09:10:14.697: *** End #16416 /api/now/table/ngbsm_script, user: david.piper@snc, total time: 0:00:00.797, processing time: 0:00:00.017, total wait: 0:00:00.780, session wait: 0:00:00.780, SQL time: 0:00:00.002 (count: 4), source: 199.91.137.60 , type:rest, method:GET, api_name:now/table, resource:now/table/ngbsm_script, version:Default, user_id:david.piper@snc, response_status:200

Workaround

This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available.

Warning: System property glide.invalid_query.returns_no_rows=true is not enabled by default, and was probably set for a very good reason on your instance. e.g. After some table/field changes caused a custom script to start querying based on field that no longer existed, and then ending up affecting a lot more data than intended. It is probably not a good idea to set that false in order to workaround this issue.


Related Problem: PRB1335398

Seen In

There is no data to report.

Intended Fix Version

New York

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-04-08 09:27:53
Published:2019-04-04