Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

Wildcard search (*) is not working on custom table

Dipali_Pawar
Tera Contributor

I have custome table which has number field and display value is true on that field when non admin user trying search number using * number it's showing no record found but same record is showing when user search with = number  and for same user description search is working correctly I have checked below configurations still not working please help me with this if anyone has faced similar kind of issue

 

1. there is one systempropery which is diabling search i tried to change value to true still not working

2. table levels acls has internal and other role , internal role user already have i have given other role as well still not working

3. I have maked display false for number still same issue 

4. There is no query BR is configured on that particular table 

2 ACCEPTED SOLUTIONS

J Siva
Kilo Patron

Hi @Dipali_Pawar 

Please check whether a Query Range (query_range) ACL exists for the custom table. I suspect that there is currently no query_range ACL configured for this table.

If one does not exist, please create a Query Range ACL for the specific table and assign the necessary roles to it.

Also, could you please confirm whether this custom table is extending another table or if it is a standalone custom table?
Regards
Siva

View solution in original post

Ankur Bawiskar
Tera Patron

@Dipali_Pawar 

things to do

-> check if there is query_range or query_match ACL for that table if not then create a new one

Query ACLs 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

6 REPLIES 6

J Siva
Kilo Patron

Hi @Dipali_Pawar 

Please check whether a Query Range (query_range) ACL exists for the custom table. I suspect that there is currently no query_range ACL configured for this table.

If one does not exist, please create a Query Range ACL for the specific table and assign the necessary roles to it.

Also, could you please confirm whether this custom table is extending another table or if it is a standalone custom table?
Regards
Siva

Ankur Bawiskar
Tera Patron

@Dipali_Pawar 

things to do

-> check if there is query_range or query_match ACL for that table if not then create a new one

Query ACLs 

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Tanushree Maiti
Tera Patron

Hi @Dipali_Pawar 

 

  • Check if there are field-level ACLs (like table_name.number) restricting read access for the user's role. Create or update the field-level Read ACL to include the required role.
  • Non-admin users might have table read access, but lack explicit field-level Read ACL permissions for the specific number field.
  • Refer : Set global text search properties 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Dipali_Pawar
Tera Contributor

Thanks @J Siva & @Ankur Bawiskar one query , the query range acl should i createonly for number field or for table level itself?