Insufficient access for 'query_range' operation on kb_knowledge.u_peer_reviewer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 04:20 AM
Hi Team,
While searching the query , 'Peer Reviewer' starts with 'User123' for example, it is throwing up an error -"insufficient access for 'query_range' operation on "kb_knowledge.u_peer_reviewer"
I have checked all the 'query_range' operation on the table and fields, there is no ACL on u_peer_reviewer field.
Not sure how to resolve this issue.
Thanks,
Rooma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 04:35 AM - edited 05-19-2025 05:08 AM
Hi @roomawakar
To resolve this, create a custom field-level "query_range" filter on the kb_knowledge table and specify the roles that should be granted access.
Check out the below post for more info.
https://www.ikconsulting.com/post/understanding-servicenow-s-may-2025-query-range-acl-update-what-you-need-to-know#:~:text=In%20May%202025%2C%20ServiceNow%20released%20a%20critical,unauthorized%20%E2%80%9Crange%E2%80%9D%20queries%20to%20retrieve%20sensitive%20information.
Regards,
Siva
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 06:08 AM
@J Siva I added query_range_role and the issue got fixed. It is mandatory to create a custom field-level ACL?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 07:39 AM
Where did you add "query_range_role" ? Can you post a screen grab for a reference?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2025 08:09 AM
@roomawakar Glad it helped.
Yes. You need to create a custom query_range ACLs as required.