ExamplesFor You
Home / Power BI DAX / INTERSECT

📈 Power BI DAX examples

INTERSECT Examples in Power BI DAX

Return rows that appear in both tables. 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

What INTERSECT does

Return rows that appear in both tables. In Power BI, the key is not only the formula itself but how it behaves with slicers, relationships, visuals and totals.

Syntax or pattern

INTERSECT(table1, table2)
✍️

5 practical business examples

1

INTERSECT in a sales report

Create a table expression grouped by product.

Repeat Customer IDs = INTERSECT(VALUES(Sales2025[Customer ID]), VALUES(Sales2026[Customer ID]))

Useful for calculated tables and advanced measures.

2

Add sales to customer list

Add a measure result to each customer row.

Repeat Customer IDs = INTERSECT(VALUES(Sales2025[Customer ID]), VALUES(Sales2026[Customer ID]))

Good for analysis tables.

3

Select key columns

Create a narrow table for a calculation.

Repeat Customer IDs = INTERSECT(VALUES(Sales2025[Customer ID]), VALUES(Sales2026[Customer ID]))

Use this to control table shape.

4

Top products table

Return only the highest selling products.

Repeat Customer IDs = INTERSECT(VALUES(Sales2025[Customer ID]), VALUES(Sales2026[Customer ID]))

Useful in calculated tables and ranking patterns.

5

Compare missing products

Find products in one list but not another.

Repeat Customer IDs = INTERSECT(VALUES(Sales2025[Customer ID]), VALUES(Sales2026[Customer ID]))

Useful for reconciliation checks.

Common mistakes to avoid

  • Using INTERSECT 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.

Related examples

📈 SUMMARIZE📈 ADDCOLUMNS📈 SELECTCOLUMNS📈 CROSSJOIN📈 All DAX examples📊 Excel examples🗄️ SQL examples

FAQ

When should I use INTERSECT in DAX?

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

Why is my INTERSECT 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 INTERSECT 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.

💡 Useful resources

Here are some ideas for you

Optional resources that may help if you are learning Power BI, building dashboards, or writing DAX measures often.

  • 📘
    Power BI books

    Learn modeling, report design and DAX patterns with structured references.

    See ideas
  • 🧠
    DAX books

    Keep a DAX reference close when building measures and troubleshooting context.

    See ideas
  • 📊
    Data visualization books

    Improve charts, dashboards and storytelling beyond the formula itself.

    See ideas
  • 🖥️
    Ultrawide monitors

    Useful for viewing the report canvas, data model and DAX editor side by side.

    See ideas
  • 🖱️
    Ergonomic mouse

    Helpful during long report-building and data-modeling sessions.

    See ideas
  • 📒
    Dashboard planning notebooks

    Sketch relationships, measures and report layouts before building.

    See ideas

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