Insufficient Access for query_match and query_range on sys_user_grmember in Test Instance
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hello Team,
I’m facing an issue in our test instance (not in dev) when working with a custom table that extends Task.
When users try to select a value in the Assign To field (after choosing an Assignment Group), the following error appears:
Part of the query on sys_user_grmember has been ignored because of insufficient access for 'query_match' operation on sys_user_grmember.group
Part of the query on sys_user has been ignored because of insufficient access for 'query_range' operation on sys_user_grmember.user
- What I’ve Tried
- - Attempted to create ACLs for query_match and query_range on sys_user_grmember, sys_user, and sys_user_group.
- - However, when creating ACLs, the group and user fields do not appear in the field picker.
- - Compared ACLs between dev and test — dev works fine, test throws the error.
- Question
- What is the correct way to configure ACLs so that the Assign To lookup works again?
- - Should I create query ACLs on sys_user, sys_user_group, and sys_user_grmember with roles like itil or admin?
- - Is there a recommended best practice for aligning ACLs between dev and test to avoid this mismatch?
- Any guidance or examples would be greatly appreciated!
- Thanks in advance,
- Anjani kumar
0 REPLIES 0
