Chart property: Calculation condition + Displayed message

Calculation condition in Power BI

Qlik can refuse to calculate a chart until a condition is true, such as fewer than 3 teams selected, and show a message instead. Power BI has no such property. You build it with measures that return BLANK and a dynamic message, or with a visual-level filter on a flag measure.

Partial / different approach DAX Reports

Short answer: Write a flag measure (1 when the condition holds), apply it as a visual-level filter "is 1", or wrap each measure in IF ( [Flag], ..., BLANK () ). Show the guidance in a card or the visual's title using a measure, with conditional formatting on the title text.

What it does in Qlik

The calculation condition is an expression evaluated before the chart. If it's false, the chart shows the displayed message and doesn't compute. It's the standard way to protect a big straight table from being opened without filters.

Qlik example

Qlik expression

// Calculation condition
Count(DISTINCT Customer) < 1000

// Displayed message
'Select up to 1000 customers to see details'

Power BI equivalent

Flag measure

DAX

Show detail =
// ALLSELECTED () ignores the visual's own rows, keeps slicers and page filters
IF ( CALCULATE ( DISTINCTCOUNT ( Sales[CustomerID] ), ALLSELECTED () ) < 1000, 1, 0 )

Detail title =
IF ( [Show detail] = 1, "Order detail",
     "Select up to 1000 customers to see details" )

Add Show detail to the table's visual-level filters with is 1, and bind the title to Detail title (Title → fx). When the condition is false the table shows no rows and the title tells the reader why.

Gotchas and behaviour differences

This isn't identical. Power BI still sends the query, although the filter makes it cheap. Qlik doesn't evaluate the chart at all.
A visual-level filter on a measure applies per row of the visual, not to the whole visual. That's why the flag uses ALLSELECTED (): without it, each row (one customer) would count 1 and pass the test.
Power BI tables already page their data. Large tables load in chunks as you scroll, so the "browser hangs" problem is less severe than in Qlik, but the query cost still matters.

Official documentation

Customizing data representation in a straight table (Calculation condition) (Qlik Help)
ISFILTERED (Microsoft Learn)
Conditional formatting in visual titles (expression-based titles) (Microsoft Learn)

GetFieldSelections(Region) GetFieldSelections and GetSelectedCount GetFieldSelections returns the selected values of a field as text, often for dynamic titles. In DAX you combine ISFILTERED, VALUES and CONCATENATEX. Partial / different approach If(cond, then, else) If and nested If Qlik's If() maps directly to DAX IF and to Power Query's if ... then ... else. Long nested Ifs are cleaner as SWITCH(TRUE(), ...). Qlik's numeric booleans (-1/0) are the main difference. Direct equivalent Only(Region) Only Only() returns a value when exactly one value is possible and null otherwise. In DAX that is SELECTEDVALUE, which also accepts an alternate result. 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.