What CROSSFILTER does
Change filter direction for a calculation. In Power BI, the key is not only the formula itself but how it behaves with slicers, relationships, visuals and totals.
Syntax or pattern
CROSSFILTER(column1, column2, direction)5 practical business examples
CROSSFILTER in a sales report
Return category from the related product table.
Product Category = RELATED(Products[Category])Works in calculated columns on the many-side table.
Count related sales rows
Count transactions for a customer.
Customer Orders = COUNTROWS(RELATEDTABLE(Sales))Useful in calculated columns for customer-level summaries.
Use ship date instead of order date
Activate an inactive date relationship.
Sales by Ship Date = CALCULATE([Total Sales], USERELATIONSHIP(Sales[Ship Date], Calendar[Date]))Good when a fact table has multiple dates.
Apply disconnected slicer values
Use a disconnected table as a filter.
Selected Segment Sales = CALCULATE([Total Sales], TREATAS(VALUES(SegmentSelector[Segment]), Customers[Segment]))Useful for custom slicer designs.
Adjust relationship direction for one measure
Change cross-filtering only inside a calculation.
Filtered Sales = CALCULATE([Total Sales], CROSSFILTER(Customers[Customer ID], Sales[Customer ID], BOTH))Use carefully when model design cannot be changed.
Common mistakes to avoid
- Using CROSSFILTER 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 CROSSFILTER in DAX?
Use CROSSFILTER when the calculation pattern matches the business question and the result behaves correctly in the current filter context.
Why is my CROSSFILTER 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 CROSSFILTER 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.