Invalid query detected - How to get more QueryEventLogger log details

[Am_lie BACHELOT]

Hi everyone,

Since few month we had to enable the sys_property "glide.invalid_query.returns_no_rows" to true, to block invalid queries (some errors were made in background scripts and caused many very problematic side effects on our instance).

Since then, we have regularly found script errors (previously unknown) which we correct over time.

This is how we will gain in quality.

The problem is that on multiple dashboard that uses interactive filters, dynamic filters... we encounter problems where we cannot identify where the query error is located. Do you know if it is possible to have more details in the QueryEventLogger logs?

In our log, we can see "QueryEventLogger: Invalid query detected, please check logs for details [Unknown field null in table task]" but it's not very precise.

Thanx for your help,

Regards,

Amélie Bachelot

[Vasantharajan N]

@Am_lie BACHELOT - Worth to go through the below KB article related to QueryEventLogger 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0779915

[abhishek_s]

In the logs (i.e. syslog), personalize to get the 'Context map' column into your list view. It is an object which provides very useful details about the transaction that generated that error. It won't point the exact component (i.e. this Business Rule or that Script Include) but it should give you the trigger / start point.