Measures

Measures are the most important type of calculation in Power BI.

A measure performs a calculation dynamically based on the current filter context. Unlike calculated columns, measures are not stored in the data model. Instead, they are evaluated each time a visual or report requests a result.

Measures are commonly used to calculate:

• Sales
• Revenue
• Profit
• Percentages
• KPIs
• Running totals
• Year-to-date values

What Is a Measure?

A measure is a reusable DAX expression.

General syntax:

Measure Name =
Expression

Example:

Total Sales =
SUM(FactSales[SalesAmount])

The measure calculates the total sales for the current report context.

Creating a Measure

Measures are created from a table in the Fields pane.

After a measure is created, it can be reused in:

• Tables
• Matrix visuals
• Cards
• Charts
• KPIs
• Other DAX measures

One measure can support dozens of report visuals.

How Measures Work

Measures are evaluated after Power BI applies report filters.

Example:

User selects:

Year = 2026
Category = Bikes

        |
        v

Power BI filters FactSales

        |
        v

Measure evaluates only visible rows

        |
        v

Returns Total Sales

The DAX formula never changes.

Only the rows being evaluated change.

Simple Measure Example

Total Quantity =
SUM(FactSales[Quantity])

Power BI adds together every visible value in the Quantity column.

If a slicer filters the report to a single year, only that year's values are included.

Measures Can Build on Other Measures

One of the biggest advantages of DAX is reusability.

Example:

Total Sales =
SUM(FactSales[SalesAmount])

Total Cost =
SUM(FactSales[Cost])

Profit =
[Total Sales] - [Total Cost]

Rather than repeating calculations, measures can reference existing measures.

This makes models easier to maintain.

Common Measure Functions

Most Power BI reports use a relatively small group of DAX aggregation functions.

Example:

Average Sales =
AVERAGE(FactSales[SalesAmount])

Example:

Customer Count =
DISTINCTCOUNT(FactSales[CustomerKey])

These functions form the foundation for many business calculations.

Measures Respond to Filter Context

Measures automatically respond to report filters, slicers, and relationships.

Suppose the report contains this measure:

Total Sales =
SUM(FactSales[SalesAmount])

The result changes depending on the report context.

The DAX expression never changes.

Only the rows being evaluated change.

Reusing Measures

One measure can be used inside another measure.

Example:

Total Sales =
SUM(FactSales[SalesAmount])

Total Cost =
SUM(FactSales[Cost])

Gross Profit =
[Total Sales] - [Total Cost]

Building calculations this way creates reusable business logic and makes maintenance much easier.

Formatting Measures

Measures should always be formatted appropriately.

Examples:

Formatting improves report readability without changing the calculation itself.

Naming Conventions

Good measure names make reports easier to understand.

Recommended:

Total Sales
Average Sales
Gross Profit
Profit Margin
Order Count

Avoid:

Measure1
Sales2
Calc
NewMeasure

Choose names that clearly describe the business calculation.

Organizing Measures

As a model grows, measures should be organized into display folders.

Example:

Measures

├── Sales
│   ├── Total Sales
│   ├── Average Sales
│   └── Sales YTD
│
├── Profit
│   ├── Gross Profit
│   ├── Profit Margin
│   └── Gross Margin %
│
└── Customers
    ├── Customer Count
    └── Average Customer Spend

A well-organized model is easier for report developers to navigate.

Common Beginner Mistakes

Avoid these common issues:

• Creating calculated columns instead of measures.
• Repeating the same calculation in multiple measures.
• Giving measures unclear names.
• Creating one extremely large measure instead of several reusable measures.
• Forgetting to format measures correctly.

Simple, reusable measures are easier to maintain and debug.

Performance Best Practices

Well-designed measures improve both report performance and maintainability.

Follow these recommendations:

• Build reusable base measures.
• Keep calculations focused on one business concept.
• Avoid repeating the same DAX logic.
• Use variables (VAR) to simplify complex calculations.
• Format measures consistently.
• Organize measures into display folders.

A small collection of reusable measures is usually better than one large, complex formula.

Using Variables

Variables make DAX easier to read and often improve performance.

Instead of repeating calculations, store intermediate results in variables.

Example:

Profit Margin =
VAR Revenue =
    [Total Sales]

VAR Profit =
    [Gross Profit]

RETURN
    DIVIDE(
        Profit,
        Revenue
    )

Benefits of variables include:

• Cleaner code
• Easier debugging
• Better readability
• Reduced repeated calculations

Real-World Business Measures

Measures are used to answer common business questions.

Examples include:

Most Power BI dashboards are built using dozens—or even hundreds—of reusable measures.

Measure Dependencies

Measures can reference other measures to build more advanced calculations.

Example:

Total Sales
      │
      ▼
Gross Profit
      │
      ▼
Profit Margin
      │
      ▼
Gross Margin %

Building calculations in layers keeps your model organized and reduces duplicated logic.

Summary

Measures are the foundation of analytical reporting in Power BI.

Unlike calculated columns, measures:

• Are evaluated dynamically.
• Respond to filter context.
• Can be reused across reports.
• Do not increase model size.
• Support interactive dashboards.

A well-designed semantic model usually contains many small, reusable measures rather than a few large, complicated formulas.

Next Steps

Continue learning DAX:

• Calculated Columns
• Filter Context
• Row Context
• CALCULATE
• Variables (VAR)
• Time Intelligence