QlikToDax

Above(Sum(Sales))

Above, Below, Before and After in Power BI

Above() reads the value from the previous row of the chart. Power BI offers three replacements: the OFFSET window function, the PREVIOUS visual calculation, and calendar-aware time intelligence. Each behaves differently when periods are missing.

Partial / different approach DAX

Short answer: For "previous row" use CALCULATE([Sales], OFFSET(-1, ALLSELECTED('Date'[YearMonth]), ORDERBY('Date'[YearMonth]))), or the visual calculation PREVIOUS([Sales]). For "previous calendar month" use DATEADD.

What it does in Qlik

Above([TOTAL] expr [, offset [, count]]) evaluates the expression on the row above the current one in the chart's column segment. Below looks down. Before and After do the same across pivot-table columns. The result depends on the chart's sort order, and the first row returns NULL.

Qlik example

Qlik chart expressions
Above(Sum(Sales))                     // previous row
Sum(Sales) - Above(Sum(Sales))        // change vs previous row
Above(Sum(Sales), 12)                 // 12 rows up (same month last year, if no gaps)

Power BI equivalent

Window function (model measure)

This assumes 'Date'[YearMonth] is a sortable column such as 202401.

DAX
Sales previous row =
CALCULATE (
    [Sales],
    OFFSET ( -1, ALLSELECTED ( 'Date'[YearMonth] ), ORDERBY ( 'Date'[YearMonth], ASC ) )
)

Visual calculation

DAX (visual calculation)
Previous = PREVIOUS ( [Sales] )
Change = [Sales] - PREVIOUS ( [Sales] )

Calendar-aware (time intelligence)

DAX
Sales previous month = CALCULATE ( [Sales], DATEADD ( 'Date'[Date], -1, MONTH ) )
Sales last year = CALCULATE ( [Sales], SAMEPERIODLASTYEAR ( 'Date'[Date] ) )

Gotchas and behaviour differences

  • Above moves by displayed row. If a month has no data and is hidden, Qlik's "previous" is the month before the gap. DATEADD always uses the calendar. OFFSET over ALLSELECTED('Date'[YearMonth]) includes empty months, because it walks the date table.
  • Above(..., 12) for "same month last year" breaks as soon as a month is missing. SAMEPERIODLASTYEAR does not.
  • The sort order in a Qlik chart changes what Above returns. OFFSET uses its own ORDERBY, independent of the visual's sort.
  • The time intelligence functions need a proper date table with contiguous dates, marked as a date table. See master calendar.

Official documentation

Related pages

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 RangeAvg(Above(Sum(Sales), 0, 3)) Moving averages with RangeAvg(Above(...)) RangeAvg(Above(Sum(Sales), 0, 3)) gives a 3-row moving average. In Power BI, use WINDOW with AVERAGEX, the MOVINGAVERAGE visual calculation, or a calendar-based DATESINPERIOD measure. Partial / different approach Previous(expr) Previous (compare with the previous input row) Previous returns an expression's value from the previous input record. Power BI has no LAG in Power Query, so use the index-shift self-merge pattern, a SQL LAG upstream, or a DAX calculated column that finds the previous value. Partial / different approach LOAD ... AUTOGENERATE ... WHILE ... IterNo() Master calendar (date table) The Qlik master calendar script maps to a date table built in Power Query (List.Dates) or DAX (CALENDAR), marked as a date table and related to the fact date. It is essential for every time-intelligence function. 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.