pbPassingBI
/
Power Query & Power Pivot advanced 9 min

Power Pivot and the Data Model

Relationships and DAX measures inside Excel, past the million-row limit.

What you'll be able to do
  • Load tables to the Data Model and relate them
  • Write a basic DAX measure
  • Explain when the Data Model beats VLOOKUP

What it adds

The Data Model is the same VertiPaq engine that powers Power BI, embedded in Excel. It holds compressed tables, relationships between them, and DAX measures.

It breaks the worksheet row limit — a worksheet caps at 1,048,576 rows, but the Data Model holds far more because data never lands on a sheet.

Relationships instead of lookups

Load a fact table and its dimensions, then create relationships in the Diagram View. A pivot built on the model can now slice the fact by any dimension attribute — no VLOOKUP columns at all.

This is faster, smaller, and does not break when someone inserts a column. For any workbook joining more than two tables, it is the right architecture.

DAX measures

In the Power Pivot window, add measures:

Total Sales := SUM(Sales[Amount])
Margin % := DIVIDE([Total Sales] - SUM(Sales[Cost]), [Total Sales])
Sales LY := CALCULATE([Total Sales], SAMEPERIODLASTYEAR('Date'[Date]))

Measures compute in the pivot's filter context, so one definition works at every level of the pivot. DISTINCTCOUNT gives correct distinct counts, which plain pivots cannot do without the model.

When to use it

Use the Data Model when you have multiple related tables, more rows than a sheet holds, a need for distinct counts, or time intelligence.

Stick with plain pivots and formulas for a single flat table under a few hundred thousand rows — the model adds complexity that small workbooks do not need.

Key points
  • Data Model = VertiPaq inside Excel; relationships replace lookup columns
  • DAX measures work at every pivot level from one definition
  • DISTINCTCOUNT and time intelligence need the model
Check yourself