Sys_user operator Starts with / ends with or Contains

[Jason Rooney]

1. Open Sys_user.list

2. One of our custom fields - do Starts with / ends with or Contains for A

3. Note Nothing will appear

4. Change operator "is not" and search for A 

5. We have results 

Why is this broken only to ONE u_ column only the first 3 operators?

 glide-yokohama-12-18-2024__patch2-hotfix2-04-15-2025

[Abbas_5]

Hello @Jason Rooney,

The error described, where only the first 3 operators are working for a single column in ServiceNow's Glide-Yokohama release patch 2-hotfix 2-04-15-2025, is likely due to a restriction or change introduced with the patch related to query_range ACLs. These ACLs control the use of range operators (like >, <, >=, <=, and BETWEEN) in queries. The patch may have tightened the defaults for these ACLs, requiring explicit permissions to be set for each column and operator that needs to be enabled, according to a community article. 

Here's a breakdown of the likely cause and potential solutions:

• Query Range ACLs:

  The patch introduced stricter defaults for query_range ACLs, meaning range queries are now blocked by default unless explicitly permitted. These ACLs need to be configured for each field where range queries are required, and they need to be assigned to the appropriate user roles. 
• Error Messages:

  Without the necessary query_range ACLs, users may encounter error messages, such as the one you've seen, indicating that they are not authorized to use range operators. 
• Troubleshooting Steps:

  • Verify ACLs: Check if the correct query_range ACLs have been defined for the affected column and operators. Also, ensure that these ACLs are assigned to the appropriate user roles. 
  • Review Documentation: Consult the ServiceNow support knowledge base or the release notes for the specific patch (Yokohama patch 2-hotfix 2-04-15-2025) for detailed information about the changes and how to address them. 
  • Contact Support: If you are unable to resolve the issue, reach out to ServiceNow support for assistance. 

By understanding the role of query_range ACLs and reviewing the relevant documentation, you should be able to pinpoint the source of the problem and take the necessary steps to resolve it.

If this is helpful, please hit the thumbs button and accept the correct solution by referring to this solution in future it will be helpful to them.

Thanks & Regards,

Abbas Shaik

[Ankur Bawiskar]

@Jason Rooney 

was this working fine earlier and broken after the upgrade?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Jason Rooney]

Yes working before - ACL (query_range ) update and or yokohama update 

[Ankur Bawiskar · Accepted solution]

@Jason Rooney  

check this link

ServiceNow Yokohama patch Query Range ACL Update – Issue Summary

If my response helped please mark it correct and close the thread so that it benefits future readers.