In a situation where the dataset contains multiple fields that could be used for comparison the analyst has a challenge to deal with... How can someone predict whether the viewer wants to compare the products, categories or brands, and measure sales by number of units sold, $ value, or the weight shipped?
One option is to create multiple variations of the same chart, using different combinations of split and measure fields.
Omniscope offers a solution to avoid the dashboard overload like that and give the end user control over the proceedings: scenario where the person 'consuming the report' is given the choice and is able to do it all on a single Omniscope tab.
The demo here is showing how interaction and choice of split/measure fields is affecting three different charts on a single tab, avoiding the need to duplicate design work.
We can achieve this by creating the split and measure formula fields in the Report's Data Sources area:
Open the target Report block in Omniscope Evo workflow > click Design or Explore button > Data Sources
On the Sources tab add the Formula block (fx) next to the data source block that contains the filter and measure fields.
![]() | ![]() |
On the Variables tab create your variables and give them a name e.g. [Split choice] and [Measure choice], then add choice values, like in the image below: "Type", "Pack", "Brand".
In this case we're using a text choice variable. Omniscope will also allow you to use integer, decimal or date values to create a different type of variable.
In the formula editor add IF formula combining your variable name and the outcome field or desired value.
In this case we are creating a simple logic: if the split choice is 'Type', then the result of the formula will be whatever value is found in the [Type] or [Brand] field, otherwise will return [Pack] value.
IF (
[Split choice]='Type',[Type],
[Split choice]='Brand',[Brand],
[Pack])
Note that your Variable choices can, but don't have to contain the exact field names - you can use different wording, if the original field name is too long. This will work as long as you match in the formula syntax the exact spelling of both [Variable] and [Field name].
Finally - make sure that you add the Filter devices with exposed split/measure Variables, so the end user can interact with them and switch between different comparison scenarios.