"Part of the query on incident has been ignored because of insufficient access for 'query_range' ope
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2025 04:57 AM - edited 05-26-2025 11:13 PM
Hi Team
Users are unable to see the report records in the dashboard after upgrade they are getting the below error
"Part of the query on incident has been ignored because of insufficient access for 'query_range' operation on sys_user.u_qs_default_group"
I found an ACL it is restricting the access to users and I modified it now error is not reflecting on the reports but the report records are still not visible to users so I'm checking on the ACL conditions and other ACL's
I checked the report level and dash board level ACLs and sys_user table & incident table level and sys_user field level ACLs and users groups and roles of the users who are able to see the report records and I added the same roles and groups to other users, but they still couldn't see the report records, so I created two new ACLs one at the table level and one at the field level for the sys user table but the report records are still not visible to those users
Could you please guide me how to resolve this issue
Thanks in advance
Have a nice day!
Thanks & Regards
Baby G
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2025 04:13 AM - edited 05-21-2025 04:19 AM
I guess you have to create a new "query_range" ACL on the "sys_user" table for the field "u_qs_default_group" for the needed "role" with the "UserIsAuthenticatedAndHasRightsToRead" Security Attribute. This is since last Monday SN globally "query_range" ACL implementation on every instances for every customers...
See my attachment as exemple
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-02-2025 05:38 AM
@BabyG ,
I’ve encountered the same issue as well. To address it, I created two ACLs with the following operations:
query_match
query_range
Based on the error you're receiving, I recommend selecting the relevant table and field, then trying again with the appropriate configuration.
If you have any further questions or need assistance, please feel free to reach out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2025 03:15 AM
Had similar issue and this post solved the issue.