Master items: reusable dimensions, measures and visualizations

Master items (master dimensions and measures) in Power BI

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 Modeling DAX Power BI service

Short answer: Turn each master measure into a DAX measure, put related measures in display folders, and give them descriptions and format strings. Master dimensions are just columns, or a calculated column if the dimension was an expression. Publish the model once and connect every report to it ("live connection") instead of copying the logic.

What it does in Qlik

A master measure is a named expression with a label, description, tags and number format. Charts reference it by name, so a change to the master item updates every chart.

Master dimensions can be a single field, a drill-down group or a cyclic group, sometimes with a calculated dimension expression.

Qlik example

Qlik expression

// Master measure "Gross margin %"
(Sum(Sales) - Sum(Cost)) / Sum(Sales)

// Master dimension "Customer size" (calculated dimension)
If(Aggr(Sum(Sales), Customer) > 100000, 'Large', 'Small')

Power BI equivalent

Master measure → model measure

DAX

Gross margin % =
DIVIDE ( [Sales] - [Cost], [Sales] )

Set the format string on the measure (Percentage) and put it in a display folder such as Margin. Descriptions show as tooltips in the Data pane, much like the master item description.

Calculated master dimension → calculated column

DAX

// Column on the Customer table, evaluated at refresh, not at query time
Customer size =
IF ( CALCULATE ( SUM ( Sales[Amount] ) ) > 100000, "Large", "Small" )

This is static: it doesn't react to slicers, unlike the Qlik Aggr version. For a dynamic bucket you need a disconnected table and a measure (see data islands).

Sharing across apps → one semantic model, many reports

Publish the model to a workspace, then create new reports with Get data → Power BI semantic models. Report authors can add report-level measures, but the governed logic stays in the shared model. Endorse it (Promoted or Certified) so people find the right one.

Gotchas and behaviour differences

Power BI has no separate "master visualization". Reuse a visual by copying it between reports, or keep a template report (.pbit).
Qlik master items can't be overridden per chart without unlinking. Power BI report authors on a live connection can create report-level measures, which then live only in that report.
A calculated master dimension that depends on selections has no direct equivalent as a column. Calculated columns are computed at refresh.

Official documentation

Creating master measures (Qlik Help)
Creating master dimensions (Qlik Help)
Create measures for data analysis in Power BI Desktop (Microsoft Learn)
Connect to semantic models in the Power BI service from Desktop (Microsoft Learn)

Avg(Aggr(Sum(Sales), Customer)) Aggr (nested aggregation) Aggr builds a virtual table of aggregated values, for example sales per customer, so you can aggregate again. In DAX that is an iterator (AVERAGEX, MAXX, COUNTROWS(FILTER(...))) over VALUES or SUMMARIZE that calls a measure. Partial / different approach 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 Cyclic master dimension, or a variable-driven dimension/measure Cyclic dimensions and dynamic measures 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 SET vSales = Sum(Sales); LET vToday = Today(); Variables (SET, LET and $-expansion) Qlik variables hold expressions, values and settings, and are expanded as text. Power BI splits these roles: measures for reusable logic, Power Query parameters for load settings, what-if and field parameters for user input, calculation groups for logic applied to many measures, and VAR inside DAX. Partial / different approach

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.