This topic discusses what Queries are and how to use them.
What is a Query?
You can think of a query as a storage location for your filter rules. This means you can create one or more storage locations (multiple queries) to store different filter settings. Once created, a query can be used as a data source for the data visualisations ('views'), to show only the data that matches those filter rules e.g. female customers, where age is between 35-45 years.
Queries will appear as devices in the Filter view, so the user can add them to the filtering menu, as ready-made data subsets with desired characteristics.
Types of Queries
There are two kinds of queries in Omniscope:
Tab specific - these queries exist in a given tab only, and are only accessible from one tab.
Multi-tab - these queries exist across all tabs, and can be used in any tab within the report.
Filtered IN query
In Omniscope all filter rules are stored in a "Query". By default, if you don't create your own queries, they get stored in a query called "Filtered IN", which always exists. This type of query is tab-specific, and each tab has its own “Filtered IN” state, which is result of the current filter states. If nothing is filtered, the views will display the whole dataset. On interaction with filter devices, by default, the views will display the data that is filtered in. You also have an option within each view to opt for the filtered out, or 'inverse' state.
Managing queries
User-created queries can be either tab-specific or multi-tab and there are two places from where you can create/manage them from:
In the Filters view, a "+ Query" button appears in the configuration mode. Use the filters devices to create the subset (e.g. Product = shoes, Price > 50), then click on the Query button to give your query a name and universe (single tab Vs all tabs)
Using the Report settings > Global tab dialogue you can rename the queries, specify whether they are 'read only', or add new queries, although the filtering that creates the desired subset has to happen as per step 1.
Dynamic vs read-only queries
Once created, Omniscope queries can still be edited and new data and filter states can modify existing queries, if desired.
The user controls whether or not those rules are dynamically updated, or are stored as “read-only”.
You can create queries which are dynamic and continuously change when the user changes filter rules. For example, if you have a multi-tab query, and you use “Filters view" to modify one of the filter rules within that query, then all the tabs containing that query will pick up the changes and update the views.
Read-only query - once created all filter rules are a set, and could no longer be modified (for as long as the query is classified as 'read only')
Dynamic query - it will allow the report creator to dynamically change it and modify the filters. This approach allows you to easily create multi-tab filter, where all the tabs share the same rules.
Advanced feature - synchronised filter behaviour across the tabs (end-user in control)
In a situation when report editor would like to enable the end user to pick a filter state on one tab, and for that choice to be reflected on all or multiple report tabs, advanced dynamic query feature could be used.
From the Report settings>General tab create a multi-tab, editable query e.g. "Mirror query"
Open the Filter device and from the Filter search/picker box navigate to the Mirror query and select the relevant field filters (from the Mirror query's filter list)
On different tabs, where the mirrored filter behaviour is required, add the Mirror query's field filter choices and point the views to the Mirror query (inside each view, from the Query options>Multi-tab>Mirror query)
This topic discusses what Queries are and how to use them.
What is a Query?
You can think of a query as a storage location for your filter rules. This means you can create one or more storage locations (multiple queries) to store different filter settings. Once created, a query can be used as a data source for the data visualisations ('views'), to show only the data that matches those filter rules e.g. female customers, where age is between 35-45 years.
Queries will appear as devices in the Filter view, so the user can add them to the filtering menu, as ready-made data subsets with desired characteristics.
Types of Queries
There are two kinds of queries in Omniscope:
Filtered IN query
In Omniscope all filter rules are stored in a "Query". By default, if you don't create your own queries, they get stored in a query called "Filtered IN", which always exists. This type of query is tab-specific, and each tab has its own “Filtered IN” state, which is result of the current filter states. If nothing is filtered, the views will display the whole dataset. On interaction with filter devices, by default, the views will display the data that is filtered in. You also have an option within each view to opt for the filtered out, or 'inverse' state.
Managing queries
User-created queries can be either tab-specific or multi-tab and there are two places from where you can create/manage them from:
Dynamic vs read-only queries
Once created, Omniscope queries can still be edited and new data and filter states can modify existing queries, if desired.
The user controls whether or not those rules are dynamically updated, or are stored as “read-only”.
You can create queries which are dynamic and continuously change when the user changes filter rules. For example, if you have a multi-tab query, and you use “Filters view" to modify one of the filter rules within that query, then all the tabs containing that query will pick up the changes and update the views.
Advanced feature - synchronised filter behaviour across the tabs (end-user in control)
In a situation when report editor would like to enable the end user to pick a filter state on one tab, and for that choice to be reflected on all or multiple report tabs, advanced dynamic query feature could be used.
1 Votes
0 Comments
Login or Sign up to post a comment