Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Snapshot is super important in reporting, especially for things like inventory, headcount, or account balances.
A snapshot is the value of something at a specific point in time (usually the last day of the month, week, or quarter).
It’s not cumulative and it’s not meant to be summed across days.
👉 Example:
If you check your bank balance every day for 10 days:
Day 1 = ₹5,000
Day 2 = ₹7,000
Day 3 = ₹6,500
Your "balance" is just one number each day.
If you summed them → ₹18,500 (nonsense!).
If you take the snapshot on Day 3 → ₹6,500 (correct).
They are measures where you want to show the state as of the last date in a period, not the sum of all rows.
Typical examples:
Inventory Stock on Hand (as of the last date of the month)
Employee Headcount (number of employees at month end)
Bank Account Balance (balance on last day)
Because in Power BI:
By default, dragging a column into Values → SUMs across all rows.
For snapshots, that inflates results.
So we use patterns like:
Stock on Hand = CALCULATE ( SUM ( Inventory[UnitsBalance] ), LASTNONBLANK ( 'Date'[Date], SUM ( Inventory[UnitsBalance] ) ) )
or
Stock on Hand = CALCULATE ( SUM ( Inventory[UnitsBalance] ), FILTER ( ALL ( 'Date'[Date] ), 'Date'[Date] = MAX ( 'Date'[Date] ) ) )
Both force Power BI to take the balance on the last available date, instead of summing all dates.
✅ In short:
Snapshot calculation = state at a point in time (last date).
Transactional calculation = sum over time (sales, revenue, etc.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.