With effect from 2022-03-24 dashboard release:
Sub-query will enable users to introduce charts as filter values, this means that charts are run as sub-queries which will help build the data of the main chart.
What is Sub-query:
In the example below:
We have a chart called ‘County Population’
This chart has been filtered using another chart called ‘US State Population’
Our ‘County Population’ chart shows the population for every state in the United States.
...
Our second chart, ‘US State Population’ shows the total population for every State in the United States but has been filtered to only show the top 10 most populous states.
...
When we use the chart, ‘State Population’, to filter our ‘County Population’ chart we will only see counties in the top 10 most populous states.
...
This works by running the SQL query of the sub- chart, ‘US State Population’, and using the values from this chart to populate the filter for the ‘County Population’ chart.
...
Please refer to this page to see a walkthrough of a sub-query filter.
How does Sub-query work:
when using an in/not in operator - the first column of the data from the sub-chart is used (multiple values, as described on the tooltip in the screenshot)
top/bottom operator - when using a top/ bottom operator, the option to select a chart to filter on will not be available
single value operator e.g. Like - the first data point (first row of the first column) is used as the filter value
After selecting what you want to filter on and the operator you want to use you will then be able to select from data or a chart when picking the value to filter on. The type of charts allowed to be used as sub-query are similar to the options that you can select from when using merged charts/ tables. If a chart can be used as a sub-chart of a merged chart or table, it can be used as sub-query. This means that
...
The screenshot below shows the chart types that can be selected from. If a chart type can not be used in a sub-query it will not be available on the' Charts' screen under ‘Type to filter’.
new screenshot
...
Why use sub-query:
Sub-query mainly enables the following capabilities:
it allows sub-chart data from another data connection, e.g.
chart 1 is from a Sales data connection
chart 2 is from a HR data connection
chart 1 can have a filter, and the value is chart 2
this means you can view the sales related to employees who take a lot of holidays
it allows sub-chart data from another chart, which is built with complex sql query structure
Performance with sub-query:
Since sub-query charts are building charts to be used by other charts, the time it takes to display a chart will be the total time it takes to build all the charts used. You can see a breakdown of these times by clicking Chart Tools>Chart Information and selecting the ‘Debug’ tab - add screenshot.
| Info |
|---|
To reduce the length of time taken to draw your chart, try to avoid using lots of sub-query references in your charts. |
Potential problems:
Cycle referencing: If Chart 1 uses Chart 2, Chart 2 uses Chart 3, Chart 3 uses either Chart 1 or Chart 2 as sub-query, the system shows an error
Sub-charts are changed: If a sub-chart is edited afterwards, you may get unexpected results on the main chart while the main chart is not likely to be broken, because the main chart simply just picks the first column or first data point of the sub-charts, it doesn’t care how the sub-charts are configured
Sub-charts not having data: again, the main chart is not likely to display data since there isn’t anything relevant