Report filters behaviour and performance for large datasets and live query

Modified on Wed, 13 Oct 2021 at 12:50 PM

When configuring a report to explore and drill down data you may want to change some filters settings to improve the overall speed and improve the user experience.

Especially in cases where you are connected to a large database table in "live query" mode, you can simplify the default filters behaviour.

Filters view options

By default Omniscope executes some auxiliary queries to understand the data, so you can better explore and drill down your dataset. 

You can always turn off some Filter view settings to reduce the extra queries performed when rendering the filters view.

Intelligent defaults

If ticked, automatically determines the type for a given filter device i.e. 'Search' or 'Choice'. Otherwise, will show text fields as 'Search'. Only applies to text fields.

For large datasets you can turn it off to reduce the queries submitted.

Preview graphs

If ticked, will show preview graphs next to each field filter showing the frequency distribution.

For large datasets you can turn it off to reduce the queries submitted.

Record count

If ticked, will show the record count for each "choice" value.

For large datasets, you can turn it off to reduce the queries submitted.

Adaptive choice/ranges

If ticked, choices and ranges will adapt to other filter choices dynamically as you interact with the app.

For large datasets, you can turn it off to reduce the queries submitted.

NOTE: If this option is ticked, you can also control on a per-device basis from the cog icon by unticking "Adopts to other filter choices".

Configure and optimise text search

Search type

A text search filter can perform a search for a "substring" or find an "exact" match.  The latter has typically faster performance.

Case sensitivity

Another thing to consider is case sensitivity. By default Omniscope will perform case-insensitive search to improve the UX for small datasets, where you typically don't want to miss a value just because the case does not perfectly match.

For big datasets this may turn into a performance issue, as the data engine or database would have to perform extra transformation to match a string in a case-insensitive fashion. Hence we recommend you to select "Case sensitive" -> Yes for large datasets or when your report is querying a DB in live query mode.

Tip: use the Normalise Case block in the workflow to harmonise the dataset values and apply uniform case rule.

Token match

You can control how Omniscope should treat the words / token you input in the filter - whether all of them must match (AND condition) or any of them (OR condition).

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article