getting an error while looking up any incident ticket
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2024 08:18 PM
part of the query on live_message has been ignored because of insufficient access for 'query_match' operation on live_message.chat_message error on servicenow

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2024 08:51 PM
@shaa066 The user may not have access to all the columns hence this error message is appearing. This is an expected behavior and the error message can be turned off using the following property.
Name : glide.db.encoded_query.field_acl_error_msg
Type : true | false
Value: false
Source: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717961
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-29-2024 10:32 PM
Hello @shaa066 ,
Check for similar issues:
https://www.servicenow.com/community/csm-forum/error-on-the-incident-form/m-p/3001818
https://www.servicenow.com/community/developer-forum/acl-error-after-upgrade/m-p/3002837#M1133833
Thank you!!
Dnyaneshwaree Satpute
Tera Guru
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2024 03:57 AM
I have seen the same error message on an instance which is on "glide-vancouver-07-06-2023__patch10-06-26-2024_07-11-2024_1109.zip". Suddenly, some users were not able to see records they saw before. It seems like this patch introduced two new operations "query_match" and "query_range". Those are not documented anywhere... We were able to prevent the error by creating new ACLs of operation "query_match" for the table/field in question. The error is now gone and users are able to see the records again. We created a case and are currently trying to get an answer what those new operations are and why they change the behavior of existing functionality.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2024 09:06 AM
Hey Philemon Anton1,
We're running into the exact same thing. Can you by chance provide the exact ACL workaround that you are talking about here. We would like to implement until a SN fix comes into place.
Any screenshot's or extra details would help a bunch as were used to creating ACL's but sometimes they can be finicky.
Alex McKelvey