unable to run query builder, when running it shows problem running query
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi,
This issue usually occurs due to invalid relationships, missing permissions, or overly complex queries.
I recommend testing the query with a single table first, then gradually adding relationships. Also, ensure you have proper access to all tables involved and check system logs for any errors.
In some cases, clearing cache or simplifying conditions also resolves the issue.
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi @keerthana219, Query Builder may fail if it too complex/large query: too many joins, large CMDB relationships, very large datasets. You can try to add at least one filter like: "sys_created_on is today". Similar issue often happens to syslog or sys_email tables when I try to open them. If my assumption is not your case, please explain more about your issue such as:
- Your roles
- Tables used in query
- Instance version (Tokyo, Utah, Vancouver, etc.)
- Does simple query work?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
as admin am able to run the query , but from user end he is not able to run the query showing it as ''problem running query''. user has cmdb_query_builder and cmdb_query_builder _read roles too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
In ServiceNow, Query Builder requires read access to all tables involved in the query. So I think you need to check Read ACL of the relevant table(s).
