
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-17-2025 02:30 PM
We have created a custom table that does not extend another table. It has a few fields that are all string fields. There are only 2 ACLs on the table, 1 read and 1 delete. The read contains the custom role and the delete contains 'nobody'.
An admin user can put '12345' in a string field search in the List view and it will return the query as "starts with 12345" and find the records. However when a non admin does it (but has the custom role), it also defaults to "starts with" but it does not show them anything. It only works if they do "Show Matching" on the record or do "=12345" - this is on any of the custom fields. If you give them a link to the record, they can open and see the record/fields. If they try to put 12345 into the out of the box number field then it works fine.
What could be causing this?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2025 05:32 AM
The reason was because I had to create a query_range ACL on the fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-17-2025 02:38 PM
@Daria6 Try checking, if the Glide.security.strict.table.acl is enabled in In the system properties (sys_properties.list). Sometimes this setting is disabled in some environments, leading to inconsistent ACL behavior

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2025 05:16 AM
This property does not exist in the instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2025 05:32 AM
The reason was because I had to create a query_range ACL on the fields.