error is coming while submitting new catalog request for non-admins
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2025 12:08 AM
How to remove below Errors:
1. "part of the query on ml_capability_definition_base has been ignored because of insufficient access for 'query_match' operation on ml_capability_definition_base.table"
2. "part of the query on ml_capability_definition_similarity has been ignored because of insufficient access for 'query_match' operation on ml_capability_definition_similarity.test_table"
in servicenow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2025 12:18 AM
the user with which session you are doing the activity doesn't have read access to that table's field "ml_capability_definition_similarity.test_table" and "ml_capability_definition_base.table"
Did you check that?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2025 12:40 AM
Looks like the required are missing at user level to access this table. Go to the module and see what role is required to access, and give that role to the user via group.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 10:04 AM
To resolve this, I accessed the specified tables and created ACLs that were assigned to the user's group.
In the case of the table ml_capability_definition_base, I created a query_match type ACL.