- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
I need solution in finding the root cause behind this issue mentioned below.
Part of the query on kb_knowledge has been ignored because of insufficient access for 'query_range' operation on kb_knowledge.u_original_publish_date.
Our filter for AQI that relies on the Original Publish Date no longer works due to the error posted in the short description
Attached is the screenshot.
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi, you need to create a query_range ACL so that your field can be accessed.
You can create a new ACL with the following fields:
- Type: record
- Operation: query_range
- Name: kb_knowledge from the table dropdown and u_original_publish_date from the field dropdown
- Under Required Roles, add the roles that should have access
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @rutujalande
The issue stems from recent field-level Query Security changes in ServiceNow. The platform now applies query_match and query_range ACL enforcement on certain date and reference fields.
Since the user executing the filter does not have query_range read access to kb_knowledge.u_original_publish_date, the filter is being ignored.
You need to create a custom query_range Access Control List (ACL) rule for the affected field.
- Navigate to System Security > Access Control in your ServiceNow instance.
- Click New to create a new ACL.
- Set the configuration as follows:
- Type: record
- Operation: query_range
- Name: kb_knowledge and select u_original_publish_date from the field dropdown.
- Roles: Add the roles required by users who need to execute this filter.
- Save the ACL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi, you need to create a query_range ACL so that your field can be accessed.
You can create a new ACL with the following fields:
- Type: record
- Operation: query_range
- Name: kb_knowledge from the table dropdown and u_original_publish_date from the field dropdown
- Under Required Roles, add the roles that should have access
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @rutujalande
The issue stems from recent field-level Query Security changes in ServiceNow. The platform now applies query_match and query_range ACL enforcement on certain date and reference fields.
Since the user executing the filter does not have query_range read access to kb_knowledge.u_original_publish_date, the filter is being ignored.
You need to create a custom query_range Access Control List (ACL) rule for the affected field.
- Navigate to System Security > Access Control in your ServiceNow instance.
- Click New to create a new ACL.
- Set the configuration as follows:
- Type: record
- Operation: query_range
- Name: kb_knowledge and select u_original_publish_date from the field dropdown.
- Roles: Add the roles required by users who need to execute this filter.
- Save the ACL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hii @Tanushree ,
Can you please specify the roles required by users who need to execute this filter.