PL-300 practice 3: year to date
The 2025 sales report shows units by month. Add a column with the units sold year to date, so the December row shows the year’s total.
The model has a marked date table, Date, related to Sales on the order date.
Your task
Create Units YTD: the units sold (Sales[Quantity]) from 1 January to the end of each month.
About this exercise
You practise exam-style task: time intelligence with TOTALYTD. 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, Units YTD, fills a Power BI-style matrix grouped by Date[Month]. 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
Units YTD =The result to build
Slicer: Year is 2025
| Month | Units YTD |
|---|---|
| Jan | 38 |
| Feb | 84 |
| Mar | 162 |
| Apr | 192 |
| May | 262 |
| Jun | 317 |
| Jul | 367 |
| Aug | 450 |
| Sep | 522 |
| Oct | 585 |
| Nov | 662 |
| Dec | 718 |
| Total | 718 |
Last updated 10 November 2026
Opening the exercise…