Part of the query on sys_choice has been ignored because of insufficient access for 'query_match'

CharlieNZ · ‎05-18-2025

I hope this is the right place for this.

We have a user that has started getting these on each Incident they view:

Part of the query on sys_choice has been ignored because of insufficient access for 'query_match' operation on sys_choice.name
Part of the query on sys_choice has been ignored because of insufficient access for 'query_match' operation on sys_choice.inactive
Part of the query on sys_choice has been ignored because of insufficient access for 'query_match' operation on sys_choice.dependent_value
Part of the query on sys_choice has been ignored because of insufficient access for 'query_match' operation on sys_choice.element

We haven't made any changes to their account. The issue wasn't there a week ago.

phgdet · ‎05-18-2025

Hi @CharlieNZ,
There is an article that has quite the same error message you got. Maybe you need to update this property.

Name: glide.db.encoded_query.field_acl_error_msg

Type: true | false

Value: false

CharlieNZ · ‎05-19-2025

Thanks, this has hidden the messages.

Robert H · ‎05-18-2025

Hello @CharlieNZ ,

Please check the ACLs on your instance. "query_match" is a new type of ACL that allows fine tuning what kind of queries users can perform.

Based on the error message you seem to have such an ACL configured for the sys_choice table. So you would have to review the roles/conditions/scripts in that ACL to find out why that particular does not get matched by that ACL, and then either adjust the user's roles, or the ACL, or create an additional ACL with criteria that would let that user pass.

More details here.

Regards,

Robert

CharlieNZ · ‎05-19-2025

When I look under ACL for query_match Operations, there is one listed:

Looking at the sys_choice table, there are no query_match operations listed.