QlikToDax

Column(1) / Column(2)

Column(n) and expression labels in Power BI

In a Qlik table, Column(n) or an expression label reuses the result of another measure column. In Power BI you reference the measure by name, which works anywhere. Visual calculations let you refer to the fields on the visual, which is the closest thing to "the column next to me".

Partial / different approach DAX Visual calculations

Short answer: Write [Margin] / [Sales] with measure names. Model measures can be reused everywhere. Inside one visual, a visual calculation such as DIVIDE([Margin], [Sales]) refers to the visual's own fields.

What it does in Qlik

Column(n) returns the value of the n-th measure column in a table, ignoring dimensions. You can also reference a measure column by its label, for example [Sales] - [Cost]. Both depend on the column order and labels in that one chart.

Qlik example

Qlik chart expressions
// measure 1: Sum(Sales)    label: Sales
// measure 2: Sum(Cost)     label: Cost
Column(1) - Column(2)
[Sales] - [Cost]

Power BI equivalent

Model measures

DAX
Sales = SUM ( Sales[Amount] )
Cost = SUM ( Sales[Cost] )
Margin = [Sales] - [Cost]
Margin % = DIVIDE ( [Margin], [Sales] )

Visual calculation (only on this visual)

DAX
Margin % = DIVIDE ( [Sum of Amount] - [Sum of Cost], [Sum of Amount] )

Gotchas and behaviour differences

  • DAX measures don't depend on column position, so reordering a table never breaks them. That's a common source of bugs in Qlik that goes away.
  • A visual calculation only exists on its visual. It can't be reused in another visual or exported in the data export. See the limitations.

Official documentation

Related pages

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 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 RangeSum(Above(Sum(Sales), 0, RowNo())) Running totals with RangeSum(Above(...)) The Qlik running-total idiom RangeSum(Above(Sum(Sales), 0, RowNo())) maps to a cumulative DAX measure, a WINDOW function, or the RUNNINGSUM visual calculation. 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.