User filters list but gets no results despite plenty of matching records and having access

Pandachan
Tera Contributor

I have a couple of users reporting that in CSM Workspace they're no longer able to filter on a currency field. They have their own personal lists that they are using, showing records from the approvals table. When viewing an un-filtered list, they can see 100 records, all with different values in the currency field (which is dot-walked from a case requiring approval). But when they attempt to add a filter on the currency field, such as greater than £100, the list returns no results, despite there being over 80 approval records associated with case records that have values greater than £100 in the currency field. This is affecting ALL lists for the approval table, and is affecting the user regardless of whether they use the CSM Workspace or the Classic UI.

 

What makes it weirder is that the same user can go to a list for the cases themselves, with the same currency field, and can add the same filter, and the list will return over 80 cases with values greater than £100. But that same filter doesn't work on the approvals table.

 

I am at a complete loss on this one.

2 ACCEPTED SOLUTIONS

Gustav Aldenbra
Kilo Sage

Hi @Pandachan,

 

This seems related to the security update that happened about a week ago.
Have you looked at this article https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2046494

View solution in original post

gaurrohi
Tera Expert

Hi @Pandachan,

ServiceNow updated the ACL configuration during the maintenance release, which changed the global behavior for query_range ACLs, as users could run range query requests and access instance data without proper authorization.

To address this, you can create a new query_range ACL specifically for the field in question

Please mark the response as the correct answer and helpful. This may help other community users to follow the correct solution.

Regards,
Rohit Singh

View solution in original post

2 REPLIES 2

Gustav Aldenbra
Kilo Sage

Hi @Pandachan,

 

This seems related to the security update that happened about a week ago.
Have you looked at this article https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2046494

gaurrohi
Tera Expert

Hi @Pandachan,

ServiceNow updated the ACL configuration during the maintenance release, which changed the global behavior for query_range ACLs, as users could run range query requests and access instance data without proper authorization.

To address this, you can create a new query_range ACL specifically for the field in question

Please mark the response as the correct answer and helpful. This may help other community users to follow the correct solution.

Regards,
Rohit Singh