Cyclic master dimension, or a variable-driven dimension/measure

Cyclic dimensions and dynamic measures in Power BI

A Qlik cyclic dimension lets the user cycle a chart through several fields. Power BI field parameters do the same: a slicer switches the field (or measure) a visual uses.

Direct equivalent Modeling DAX

Short answer: Modeling → New parameter → Fields, add the columns (or measures) in order, and keep "Add slicer to this page" ticked. Then use the parameter as the visual's axis. For measures with shared logic, a SWITCH on a disconnected table or a calculation group also works.

What it does in Qlik

A cyclic master dimension holds a list of fields. Charts show one at a time and the user cycles through them with a button.

A common hand-built alternative uses a variable or a data island field with $(=...) expansion to swap the dimension or measure.

Qlik example

Qlik expression

// Cyclic master dimension "Geo": Country → Region → City

// Hand-built measure switch driven by a data island field MeasureName
Pick(Match(Only(MeasureName), 'Sales', 'Margin', 'Units'),
     Sum(Sales), Sum(Margin), Sum(Units))

Power BI equivalent

Field parameter (generated by Desktop)

DAX

Geo = {
    ( "Country", NAMEOF ( 'Customer'[Country] ), 0 ),
    ( "Region",  NAMEOF ( 'Customer'[Region] ),  1 ),
    ( "City",    NAMEOF ( 'Customer'[City] ),    2 )
}

Put Geo on the visual's axis and add a single-select slicer on it. The same works with measures: NAMEOF ( [Sales] ) and so on.

Measure switch (works in any visual, including cards)

DAX

Selected measure =
SWITCH (
    SELECTEDVALUE ( 'Measure picker'[Measure], "Sales" ),
    "Sales",  [Sales],
    "Margin", [Margin],
    "Units",  [Units]
)

Gotchas and behaviour differences

Field parameters are built in Power BI Desktop (Modeling → New parameter). Check the current docs for preview status and limitations before you rely on them in production.
The SWITCH measure returns one format for every branch unless you add a dynamic format string. Field parameters keep each measure's own format.
Qlik cycles on a button inside the chart. Power BI needs a slicer or a button with bookmarks.

Official documentation

Creating a cyclic dimension (Qlik Help)
Let report readers use field parameters to change visuals (Microsoft Learn)
Calculation groups (Microsoft Learn)
SWITCH (dax.guide)

Pick(n, expr1, expr2, ...) Pick (and Pick(Match()) measure switching) Pick(n, ...) returns the n-th expression. It maps to SWITCH. The common Qlik measure-selector idiom Pick(Match(vMeasure, ...)) is better rebuilt with Power BI field parameters. Direct equivalent Island table with no key to the model, used by expressions Data islands (disconnected tables) A Qlik data island is a table with no field in common with the model; expressions read its selection. Power BI has the same idea: a disconnected table without relationships, used in a slicer and read with SELECTEDVALUE inside measures. Direct equivalent Master items: reusable dimensions, measures and visualizations Master items (master dimensions and measures) Qlik master items are governed, reusable expressions stored in the app. In Power BI the equivalent is a measure in the semantic model. Every measure is reusable by default. To share across reports, publish one semantic model and build thin reports on it. Partial / different approach Drill-down master dimension (Year → Quarter → Month) Drill-down groups A Qlik drill-down dimension moves to the next field when the user selects a single value. Power BI does the same with a hierarchy (or several fields stacked on the axis) and the drill buttons on the visual. Direct equivalent

Spotted an error or a better pattern? QlikToDax is maintained by a working BI consultant; corrections are welcome via the About page. Last reviewed 2026-10-25.