Business Intelligence, Data Visualization, Microsoft Certification, PL-300, Power BI

Create Visual Calculations by Using DAX (PL-300 Exam Prep)

 
This post is a part of the PL-300: Microsoft Power BI Data Analyst Exam Prep Hub; and this topic falls under these sections:
Visualize and analyze the data (25–30%)
   --> Create reports
      --> Create Visual Calculations by Using DAX

Note that there are 10 practice questions (with answers and explanations) at the end of each topic. Also, there are 2 practice tests with 60 questions each available on the hub below all the exam topics.

Overview

Visual calculations are a relatively new Power BI capability that allow report authors to create DAX-based calculations directly on visuals, rather than in the data model. For the PL-300 exam, this topic tests your understanding of when and why visual calculations should be used, how they differ from traditional DAX measures, and what problems they are designed to solve.

This topic is about report-level analytics, not data modeling.

What Are Visual Calculations?

Visual calculations are DAX expressions created within a visual that operate on the data already displayed in that visual.

Key characteristics:

  • Defined at the visual level
  • Do not create reusable model measures
  • Respect the visual’s existing context (rows, columns, and filters)
  • Designed for quick, lightweight calculations

Visual calculations help reduce model complexity while enabling fast analytical insights.

How Visual Calculations Differ from Measures

Understanding this distinction is critical for the exam.

Traditional DAX Measures

  • Created in the data model
  • Reusable across multiple visuals
  • Evaluated in filter context
  • Best for standardized business logic

Visual Calculations

  • Created inside a single visual
  • Not reusable outside that visual
  • Evaluated based on the visual’s layout
  • Best for ad hoc analysis and comparisons

On the exam, if a scenario mentions temporary analysis, visual-only logic, or reducing model clutter, visual calculations are likely the correct approach.

Common Use Cases for Visual Calculations

Visual calculations are ideal when:

  • You need a quick comparison within a visual
  • The calculation is not needed elsewhere
  • You want to avoid adding many measures to the model
  • The calculation depends on visual ordering or grouping

Examples of Visual Calculations

While you are not required to write complex syntax on the PL-300 exam, you should recognize common patterns.

Running Totals

Calculating cumulative values across rows displayed in a table or matrix.

Percent of Total

Showing each row’s contribution relative to the total visible in the visual.

Difference from Previous Value

Comparing values between consecutive rows, such as month-over-month changes.

Ranking

Ranking items based on the values displayed in the visual.

These calculations operate within the visual’s data scope, not across the entire dataset.

Why Visual Calculations Matter for Report Design

Visual calculations support better report design by:

  • Keeping the semantic model clean
  • Allowing report authors to experiment quickly
  • Making visuals easier to maintain
  • Reducing the need for complex DAX measures

For PL-300, this aligns with the broader goal of creating efficient, user-friendly reports.

Limitations of Visual Calculations

The exam may test awareness of what visual calculations cannot do.

Limitations include:

  • Not reusable across visuals
  • Not available for report-level KPIs
  • Not intended for enterprise-wide business logic
  • Not suitable for calculations needed in multiple reports

If a calculation must be consistent, governed, or reused, a traditional DAX measure is the better choice.

When to Use Visual Calculations vs. Measures

Use Visual Calculations When:

  • The logic is visual-specific
  • The calculation is exploratory
  • You want quick insights
  • Reuse is not required

Use Measures When:

  • The logic is business-critical
  • The calculation must be reused
  • The model must remain consistent
  • Multiple visuals depend on the same logic

PL-300 Exam Tip

Exam questions often frame this topic as a design decision.

Ask yourself:

“Does this calculation belong only to this visual, or does it belong in the model?”

  • Only this visual → Visual calculation
  • Reusable logic → Measure

Key Takeaways

  • Visual calculations use DAX at the visual level
  • They simplify report development and reduce model complexity
  • They are ideal for quick, visual-specific analysis
  • PL-300 focuses on when to use them, not advanced syntax

Practice Questions

Go to the Practice Exam Questions for this topic.

Leave a comment