Troubleshooting Combined Query issues
Who is this article for?Users who are attempting to troubleshoot issues with combined queries.
Module *_Query or higher permissions are required.
As Combined Queries pull together several existing Queries to produce results, there is room for issues if they are not set up correctly. This article will cover the two most frequent problem scenarios.
In this article:
- Query cannot be accessed
- Query layering
- Further reading
1. Query cannot be accessed
One of the error screens you can encounter contains the following message:
To troubleshoot the issue, open the Combined Query and check the Queries used.
There are two reasons why this error would occur.
'Item is not found' means that the system cannot find the item, likely because the Query has been deleted. Check the Audit Trail to confirm the history of the Query.
To resolve this issue, remove the affected Query as a filter item and create a replacement Query.
'You do not have permission to view this item.' means that the User does not have the correct permissions to view the Query, which will prevent them from using the Combined Query.
To rectify this problem, make sure the User has the correct Permissions and Ownerships of the Queries used in the Combined Query.
2. Query layering
Combined Queries cannot be used within other Queries and if you do accidentally combine them, you'll encounter issues when trying to run them.
When you drill into the filters of a Query using a Combined Query, you'll see the following:
If you select 'Parent Test 1 & 2' from the filter tab, you should be able to open the Query successfully and see that it is also using a Combined Query ('Test 1' and 'Test 2').
Attempting to open either of the Queries from this filter tab will redirect you to the error screen from before, as the system is not able to identify them correctly:
To resolve this, make sure that you don't use a Combined Query as a filter within another Combined Query.