- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-23-2024 03:57 PM
What would be the cause of the following error message when I try to create a new list - simple visualisation.
Solved! Go to Solution.
- 6,043 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2024 03:54 PM
Hi everyone,
We received the following solution for this issue from ServiceNow support:
Issue:
PA List Visualisation Error - Part of query on sys_dictionary has been ignoredInvestigation Summary:
After investigating, I have found that the following KB0717961 >>
- https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717961
is mentioning this is expected behaviour "The system does not filter to use columns that a user does not have access to. This message simply lets us know why the filter isn't what it is expected to be."The workaround for this is by setting this property:
Name : glide.db.encoded_query.field_acl_error_msg
Type : true | false
Value: falseI
Solution Proposed:
Please follow the Workaround in the KB0717961 mentioned above and set system property "glide.db.encoded_query.field_acl_error_msg" to false to resolve the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2024 05:43 AM
I opened a support case w/ SN on this. Their response is as follows:
Our development reviewed the issue and confirmed that the issue is not a problem but working as expected. This error you are seeing is because of the difference of behavior.
1. Create a new ACL for sys_dictionary with the operation as "query_match" Name: sys_dictionary field: * operation: query_match Role - Specify the role, based on your requirement.
2. Create the following system property to prevent the errors from popping up. Name: glide.db.encoded_query.field_acl_error_msg Type: true | false Value: false
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2024 05:56 AM
The issue with that solve is that it doesn't address the problem, it only hides the error message. What I have been able to identify at this time is it looks as if these items are failing due to Cross Scope elements (Global and then Scope A) - so if the item (which in my case is a Catalog item) receives the error message on "Submit" - the message appears. Having reviewed this in our Dev instance, I have created the ACL elements in the Global Scope and the Scope A application and am retesting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2025 12:11 PM
What is funny is I'm not getting these messages in MY ServiceNow instance - I get this when I am logged into ServiceNow Hi and submit a case. I opened a HI ticket we will see what they say.