📈 Power BI DAX examples

COALESCE Examples in Power BI DAX

Return the first non-blank expression. This page gives you the syntax, five practical business examples, common mistakes, and copy-ready DAX you can adapt for reports.

Updated 2026-06-125 business examplesCopy-ready DAX

💡 Ideas for You

Learning resources for Power BI measures, DAX patterns and reporting.

4 useful links

Some links in this section may be affiliate links. Choose only what is useful for your own work.

What COALESCE does

Return the first non-blank expression. In Power BI, the key is not only the formula itself but how it behaves with slicers, relationships, visuals and totals.

Syntax or pattern

COALESCE(expression1, expression2, ...)
✍️

5 practical business examples

1

COALESCE in a sales report

Classify orders as profitable or not.

Profit Flag = IF([Profit] > 0, "Profitable", "Loss")

Useful in tables and conditional formatting.

2

Create performance band

Return a simple KPI status from a measure.

Sales Status = SWITCH(TRUE(), [Sales Growth %] >= 0.1, "Strong", [Sales Growth %] >= 0, "Stable", "Needs attention")

SWITCH TRUE is a clean way to create business bands.

3

Avoid divide by zero

Calculate margin safely.

Margin % = DIVIDE([Profit], [Total Sales], 0)

DIVIDE is better than the slash operator for report measures.

4

Replace blank with zero

Show zero when a measure has no value.

Sales Display = COALESCE([Total Sales], 0)

Use this when blanks would confuse report readers.

5

Check missing target

Show a message when no target exists.

Target Check = IF(ISBLANK([Target Sales]), "No target", "Target set")

Helpful for KPI quality control.

Common mistakes to avoid

  • Using COALESCE before checking whether the data model has the right relationships and filter direction.
  • Writing one complex measure instead of creating simple base measures first.
  • Testing only at the total level and not checking row, category and date contexts.
  • Forgetting that slicers, visuals and relationships can all change the filter context.

FAQ

When should I use COALESCE in DAX?

Use COALESCE when the calculation pattern matches the business question and the result behaves correctly in the current filter context.

Why is my COALESCE measure returning the wrong total?

Most total issues come from row context, filter context, relationships, or using a column aggregation where an iterator or CALCULATE pattern is needed.

Can I use this COALESCE pattern in a calculated column?

Some patterns work in calculated columns, but most reporting calculations should be measures so they respond to slicers and report filters.