Skip to main content Skip to complementary content

Mode - chart function

Mode() finds the most commonly occurring value, the mode value, in the aggregated data. The Mode() function can process text values as well as numeric values.

Syntax:  

Mode({[SetExpression] [TOTAL [<fld {,fld}>]]} expr)

Return data type: dual

Arguments
Argument Description
expr The expression or field containing the data to be measured.
SetExpression By default, the aggregation function will aggregate over the set of possible records defined by the selection. An alternative set of records can be defined by a set analysis expression.
TOTAL If the word TOTAL occurs before the function arguments, the calculation is made over all possible values given the current selections, and not just those that pertain to the current dimensional value, that is, it disregards the chart dimensions.

By using TOTAL [<fld {.fld}>], where the TOTAL qualifier is followed by a list of one or more field names as a subset of the chart dimension variables, you create a subset of the total possible values.

Defining the aggregation scope

Example: Chart expressions
Example Result
Mode(UnitSales) Returns the most commonly occurring value in UnitSales.

Returns NULL (-). No single value occurs more often than another.

Mode(Customer) Returns the most commonly occurring value in Customer.

Returns NULL (-). No single value occurs more often than another.

Mode(TOTAL UnitSales) The TOTAL qualifier returns the most commonly occurring value in Unitsales disregarding the chart dimensions.
Mode({1} TOTAL UnitSales) The set analysis expression {1} defines the set of records to be evaluated as ALL, independent of any selection made. For example, if a specific customer is selected, it will still return the most commonly occurring value of UnitSales across the full dataset.

Example - Mode fundamentals

Example - Mode scenario to determine anomalies in sales data

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!