Products per customer with CROSSFILTER
Filters flow from the one side to the many side: from Customer to Sales, from Product to Sales. A customer row filters Sales, but not Product, so COUNTROWS(Product) shows all 8 products for every customer.
CROSSFILTER(Sales[ProductKey], Product[ProductKey], BOTH) lets the filter on Sales flow on to Product for one calculation. Then Product only keeps the products the customer bought.
Your task
Write Products Bought: COUNTROWS(Product), counted with the Sales–Product relationship filtering in both directions.
About this exercise
You practise filter direction with CALCULATE, CROSSFILTER and COUNTROWS. The exercise runs on a small bike-shop model with a Sales fact table and Product, Customer and Date dimensions, the same star schema in every lesson.
Your measure, Products Bought, fills a Power BI-style matrix grouped by Customer[Customer] and Date[Year]. As in a real report, each cell evaluates the measure in its own filter context, and the subtotals and the grand total are evaluated again in theirs rather than added up. When you check your answer, every cell is compared with the expected value, wrong cells are marked, and the hint is about the mistake you made.
Measures that already exist in the model: Sales Amount. Reference them in square brackets, for example [Sales Amount].
Where you start
Products Bought =The result to build
| Year | |||
|---|---|---|---|
| Customer | 2024 | 2025 | Total |
| Anna Berger | 7 | 7 | 8 |
| Cycles Marchand | 7 | 7 | 8 |
| Emma Clarke | 1 | 1 | |
| Fietsen De Vries | 6 | 7 | 7 |
| Jonas Weber | 7 | 6 | 8 |
| Léa Moreau | 5 | 5 | 7 |
| Northside Bikes | 8 | 8 | 8 |
| Oliver Hughes | 5 | 3 | 7 |
| Sanne Bakker | 6 | 4 | 8 |
| Velo Haus | 7 | 8 | 8 |
| Total | 8 | 8 | 8 |
Last updated 10 November 2026
Opening the exercise…