Category: Business Intelligence

Describe features of data models in Power BI (DP-900 Exam Prep)

This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub. 
This topic falls under these sections:
Describe an analytics workload (25–30%)
--> Describe data visualization in Microsoft Power BI
--> Describe features of data models in Power BI


Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

A data model is the foundation of any effective report in Microsoft Power BI. It defines how data is structured, related, and calculated, enabling efficient analysis and meaningful visualizations.

For the DP-900 exam, you should understand how data models work, their key components, and best practices.


What Is a Data Model in Power BI?

A data model is a logical representation of data that includes:

  • Tables
  • Relationships
  • Calculations

It allows Power BI to:

  • Combine data from multiple sources
  • Enable filtering and aggregation
  • Support interactive reporting

Key Features of Power BI Data Models


1. Tables

Data models consist of one or more tables, which can come from:

  • Databases
  • Files (Excel, CSV)
  • Cloud sources

✔ Tables contain rows (records) and columns (fields)


2. Relationships

Relationships define how tables are connected.

Types of Relationships

  • One-to-many (1:*) → Most common
  • Many-to-one (*:1)
  • Many-to-many (:)

Key Concepts

  • Primary key → Unique identifier in one table
  • Foreign key → Reference in another table

✔ Relationships enable filtering across tables


3. Schema Design (Star Schema)

Power BI models commonly follow a star schema:

  • Fact tables → Contain measurable data (e.g., sales)
  • Dimension tables → Contain descriptive data (e.g., customer, product)

✔ This structure improves performance and usability


4. Measures and Calculated Columns

Power BI uses DAX (Data Analysis Expressions) for calculations.

Measures

  • Calculated at query time
  • Used in aggregations (e.g., SUM, AVERAGE)

Calculated Columns

  • Computed during data load
  • Stored in the model

✔ Measures are preferred for performance


5. Data Types

Each column has a defined data type:

  • Text
  • Number
  • Date/Time
  • Boolean

✔ Correct data types ensure accurate calculations and visuals


6. Hierarchies

Hierarchies allow users to drill down into data.

Example

  • Year → Quarter → Month → Day

✔ Used for interactive reporting and exploration


7. Filtering and Cross-Filtering

Relationships enable:

  • Filter propagation between tables
  • Cross-filtering in visuals

✔ Example:
Selecting a product filters related sales data


8. Data Granularity

Granularity refers to the level of detail in data.

  • Fine-grained → detailed (e.g., individual transactions)
  • Coarse-grained → summarized (e.g., monthly totals)

✔ Consistent granularity is important for accurate analysis


9. Model Optimization

Well-designed models:

  • Use fewer tables when possible
  • Avoid unnecessary columns
  • Use measures instead of calculated columns
  • Follow star schema design

✔ Improves performance and usability


10. Relationships Direction (Filter Direction)

Relationships can filter:

  • Single direction (default, recommended)
  • Both directions (used cautiously)

✔ Incorrect settings can lead to ambiguous results


Typical Data Modeling Workflow in Power BI

  1. Load data into Power BI
  2. Clean and transform data (Power Query)
  3. Define relationships
  4. Create measures and calculations
  5. Build reports and visuals

Why This Matters for DP-900

On the exam, you may be asked to:

  • Identify components of a data model
  • Understand relationships and keys
  • Differentiate between measures and calculated columns
  • Recognize star schema design
  • Understand filtering behavior

Summary — Exam-Relevant Takeaways

✔ A data model includes:

  • Tables
  • Relationships
  • Calculations

✔ Key features:

  • Relationships (1:*, :)
  • Star schema (fact + dimension tables)
  • Measures vs calculated columns
  • Hierarchies and filtering

✔ Best practices:

  • Use star schema
  • Prefer measures over calculated columns
  • Maintain consistent granularity

✔ Exam tips:
👉 Fact table = metrics (numbers)
👉 Dimension table = descriptive attributes
👉 Measure = dynamic calculation
👉 Calculated column = stored value


Go to the Practice Exam Questions for this topic.

Go to the DP-900 Exam Prep Hub main page.

Practice Questions: Describe features of data models in Power BI (DP-900 Exam Prep)

Practice Questions


Question 1

What is the primary purpose of a data model in Power BI?

A. To store raw files
B. To define relationships and enable data analysis
C. To manage network connections
D. To create dashboards only

Answer: B

Explanation:
A data model organizes data and defines relationships and calculations for analysis.


Question 2

Which component connects tables together in a Power BI data model?

A. Measures
B. Relationships
C. Dashboards
D. Queries

Answer: B

Explanation:
Relationships define how tables interact and allow filtering across them.


Question 3

Which type of relationship is MOST common in Power BI models?

A. Many-to-many
B. One-to-many
C. One-to-one
D. No relationship

Answer: B

Explanation:
The one-to-many (1:*) relationship is the most common in analytical models.


Question 4

In a star schema, which table typically contains numeric values used for analysis?

A. Dimension table
B. Lookup table
C. Fact table
D. Bridge table

Answer: C

Explanation:
Fact tables store measurable data (e.g., sales, revenue).


Question 5

What is the role of a dimension table in a data model?

A. Store raw transaction data
B. Store aggregated values only
C. Provide descriptive attributes for filtering and grouping
D. Execute calculations

Answer: C

Explanation:
Dimension tables contain descriptive data like customer or product details.


Question 6

Which type of calculation is evaluated at query time in Power BI?

A. Calculated column
B. Measure
C. Table relationship
D. Data type

Answer: B

Explanation:
Measures are calculated dynamically during query execution.


Question 7

Which language is used to create measures and calculated columns in Power BI?

A. SQL
B. Python
C. DAX
D. Java

Answer: C

Explanation:
DAX (Data Analysis Expressions) is used for calculations in Power BI.


Question 8

What is the benefit of using a star schema in Power BI?

A. Increased data duplication
B. Simplified relationships and improved performance
C. Elimination of fact tables
D. Reduced data types

Answer: B

Explanation:
Star schema improves performance and usability by simplifying relationships.


Question 9

What happens when you create a relationship between two tables?

A. Data is duplicated
B. Tables are merged into one
C. Filters can propagate between tables
D. Data types are changed

Answer: C

Explanation:
Relationships allow filtering across related tables.


Question 10

Which feature allows users to drill down through levels such as Year → Month → Day?

A. Measures
B. Hierarchies
C. Relationships
D. Dashboards

Answer: B

Explanation:
Hierarchies enable drill-down analysis in reports.


✅ Quick Exam Takeaways

✔ Data model components:

  • Tables
  • Relationships
  • Measures & calculated columns

✔ Key concepts:

  • Fact table → numeric data
  • Dimension table → descriptive data
  • Relationships → connect tables

✔ Calculations:

  • Measures → dynamic
  • Calculated columns → stored

✔ Design best practice:

  • Use star schema

✔ Exam tip:
👉 Measure = calculated at query time
👉 Calculated column = stored in table
👉 Fact = numbers, Dimension = descriptions


Go to the DP-900 Exam Prep Hub main page.

Identify capabilities of Power BI (DP-900 Exam Prep)

This post is a part of the DP-900: Microsoft Azure Data Fundamentals Exam Prep Hub. 
This topic falls under these sections:
Describe an analytics workload (25–30%)
--> Describe data visualization in Microsoft Power BI
--> Identify capabilities of Power BI


Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

Microsoft Power BI is Microsoft’s business intelligence (BI) and data visualization platform. It enables users to connect to data, transform it, and create interactive reports and dashboards for data-driven decision-making.

For the DP-900 exam, you should understand what Power BI can do, its core components, and its role in an analytics solution.


What Is Power BI?

Power BI is a self-service and enterprise BI tool that allows users to:

  • Connect to multiple data sources
  • Transform and model data
  • Create visualizations and reports
  • Share insights across an organization

Core Capabilities of Power BI


1. Data Connectivity

Power BI can connect to a wide range of data sources:

  • Cloud services (Azure, SaaS apps)
  • Databases (SQL Server, Azure SQL)
  • Files (Excel, CSV)
  • Streaming data sources

✔ Supports both import and direct query modes


2. Data Transformation (Power Query)

Power BI includes Power Query, a tool for:

  • Cleaning data
  • Shaping and transforming data
  • Merging and filtering datasets

✔ Uses a visual interface (no coding required, though M language is available)


3. Data Modeling

Power BI enables users to create data models by:

  • Defining relationships between tables
  • Creating calculated columns and measures
  • Using DAX (Data Analysis Expressions)

✔ Supports star schema design (common in analytics)


4. Data Visualization

Power BI provides a rich set of visualizations:

  • Charts (bar, line, pie, etc.)
  • Tables and matrices
  • Maps and geographic visuals
  • KPIs and gauges

✔ Visuals are interactive and dynamic


5. Reports

A report in Power BI:

  • Is a collection of visualizations
  • Typically spans multiple pages
  • Allows filtering, slicing, and drill-down

✔ Built in Power BI Desktop and published to the cloud


6. Dashboards

A dashboard:

  • Is a single-page view of key metrics
  • Displays pinned visuals from reports
  • Provides a high-level overview

✔ Used for quick insights and monitoring


7. Data Refresh

Power BI supports:

  • Scheduled refresh (periodic updates)
  • Real-time/streaming data updates

✔ Ensures reports reflect current data


8. Sharing and Collaboration

Power BI enables users to:

  • Publish reports to the Power BI Service
  • Share dashboards with others
  • Collaborate across teams

✔ Integrates with Microsoft 365 (Teams, SharePoint)


9. Security

Power BI provides:

  • Row-Level Security (RLS)
  • Data access controls
  • Integration with Azure Active Directory

✔ Ensures users only see authorized data


10. Integration with Azure and Microsoft Ecosystem

Power BI integrates with:

  • Azure Synapse Analytics
  • Azure Data Lake Storage
  • Microsoft Fabric
  • Excel and other Microsoft tools

✔ Plays a key role in end-to-end analytics solutions


Power BI Components


Power BI Desktop

  • Authoring tool for reports
  • Installed on a local machine

Power BI Service

  • Cloud-based platform
  • Used for sharing and collaboration

Power BI Mobile

  • View dashboards and reports on mobile devices

Typical Analytics Workflow with Power BI

  1. Connect to data sources
  2. Transform data (Power Query)
  3. Model data (relationships, DAX)
  4. Create visualizations
  5. Publish reports
  6. Share dashboards

Why This Matters for DP-900

On the exam, you may be asked to:

  • Identify Power BI capabilities
  • Differentiate between reports and dashboards
  • Understand data connectivity and refresh options
  • Recognize Power BI’s role in analytics solutions

Summary — Exam-Relevant Takeaways

✔ Power BI is used for:

  • Data visualization
  • Reporting
  • Business intelligence

✔ Key capabilities:

  • Data connectivity
  • Data transformation (Power Query)
  • Data modeling (relationships, DAX)
  • Interactive visualizations
  • Sharing and collaboration

✔ Key components:

  • Power BI Desktop → report creation
  • Power BI Service → sharing
  • Dashboards → single-page overview
  • Reports → multi-page detailed analysis

✔ Exam tips:
👉 Report = multi-page, detailed
👉 Dashboard = single-page, summary
👉 Power Query = data transformation
👉 DAX = calculations and measures


Go to the Practice Exam Questions for this topic.

Go to the DP-900 Exam Prep Hub main page.

Practice Questions: Identify capabilities of Power BI (DP-900 Exam Prep)

Practice Questions


Question 1

What is the primary purpose of Microsoft Power BI?

A. Managing databases
B. Running virtual machines
C. Creating reports and visualizations from data
D. Developing applications

Answer: C

Explanation:
Power BI is a business intelligence tool used to create reports, dashboards, and visualizations.


Question 2

Which Power BI component is used to create reports?

A. Power BI Service
B. Power BI Mobile
C. Power BI Desktop
D. Azure Portal

Answer: C

Explanation:
Power BI Desktop is the primary tool for building reports and data models.


Question 3

What is the main difference between a report and a dashboard in Power BI?

A. Reports are single-page, dashboards are multi-page
B. Reports are multi-page, dashboards are single-page
C. Reports are only for developers
D. Dashboards cannot contain visuals

Answer: B

Explanation:
Reports are multi-page and detailed, while dashboards are single-page summaries.


Question 4

Which feature in Power BI is used to clean and transform data?

A. DAX
B. Power Query
C. Power Pivot
D. Azure Data Factory

Answer: B

Explanation:
Power Query is used for data transformation and preparation.


Question 5

Which language is used in Power BI for creating calculations and measures?

A. SQL
B. Python
C. DAX
D. Java

Answer: C

Explanation:
DAX (Data Analysis Expressions) is used for calculations and measures.


Question 6

Which Power BI feature allows users to restrict data access to specific rows?

A. Data refresh
B. Row-Level Security (RLS)
C. Power Query
D. Dashboards

Answer: B

Explanation:
Row-Level Security (RLS) ensures users only see data they are authorized to access.


Question 7

Which of the following is a key capability of Power BI?

A. Running operating systems
B. Hosting web applications
C. Connecting to multiple data sources
D. Managing network traffic

Answer: C

Explanation:
Power BI can connect to many different data sources, including databases, files, and cloud services.


Question 8

Where are Power BI reports typically published for sharing and collaboration?

A. Power BI Desktop
B. Power BI Service
C. Azure Virtual Machines
D. SQL Server

Answer: B

Explanation:
Reports are published to the Power BI Service for sharing and collaboration.


Question 9

Which capability allows Power BI to display near real-time data?

A. Scheduled refresh only
B. Streaming datasets
C. Static reports
D. Data export

Answer: B

Explanation:
Streaming datasets enable real-time or near real-time updates.


Question 10

What is the purpose of a Power BI dashboard?

A. To store raw data
B. To create data pipelines
C. To provide a single-page view of key metrics
D. To manage user accounts

Answer: C

Explanation:
Dashboards provide a high-level, single-page summary of important data.


✅ Quick Exam Takeaways

✔ Power BI is used for:

  • Data visualization
  • Reporting
  • Business intelligence

✔ Key features:

  • Power Query → data transformation
  • DAX → calculations
  • Reports → multi-page
  • Dashboards → single-page

✔ Components:

  • Power BI Desktop → build reports
  • Power BI Service → share and collaborate

✔ Security:

  • Row-Level Security (RLS)

✔ Exam tip:
👉 Transform data → Power Query
👉 Create calculations → DAX
👉 Share reports → Power BI Service


Go to the DP-900 Exam Prep Hub main page.

How to update the number format of the card visual in Power BI

Don’t pull your hair out … 😊

In more recent versions of Power BI, to change the display format of your measure in a card visual, do the following …

Click on the card visual. Then go the format pane (paintbrush), and the “Visual” tab within it.

Expand the “Callout” section.  Change the “Apply settings to” dropdown from “All” to the measure you want to change.

Scroll down, and change the “Display Units” parameter to your desired setting (“None” is also an option).

Optionally, if you do not already have the outcome you need from the above change, you can go to the “General” tab and make changes to the “Data format” parameters (such as decimal places, percentage, comma separator for thousands, etc) to get the exact number format that you want.

Good luck on your data journey!

How AI Is Changing Analytics (and How It Isn’t) — A Power BI and Modern Analytics Perspective

If you use Power BI or other modern data platforms today, you don’t have to look far to see AI everywhere:

  • Copilot inside Power BI and Fabric
  • Natural language Q&A visuals
  • Auto-generated DAX and measures
  • Smart narratives
  • Automated insights
  • Forecasting visuals
  • AutoML in Fabric
  • AI-assisted data prep

It may appear like analytics is becoming fully automated.

In reality, what’s happening is more nuanced.

AI is reshaping how analytics teams work — but it hasn’t replaced the fundamentals that actually make analytics valuable.

Let’s look at both sides through the lens of Power BI and today’s analytics stack.


How AI Is Changing Analytics

1. Power BI Is Becoming an “Analytics Co-Pilot”

With Copilot and built-in AI features, Power BI increasingly behaves like a smart assistant.

You can now:

  • Generate report pages from prompts
  • Create measures using natural language
  • Ask Copilot to explain DAX
  • Get auto-generated summaries of visuals
  • Build starter models and layouts

Instead of starting from a blank canvas, analysts can begin with a rough first draft produced by AI.

This doesn’t eliminate the need for modeling or design — but it dramatically reduces setup time.

The result: faster prototyping and quicker iteration.


2. Natural Language Q&A Is Expanding Self-Service Analytics

Power BI’s Q&A visual allows business users to type:

“Show total sales by region for last quarter.”

Power BI translates this into queries and visuals automatically.

This is part of a broader trend across platforms: conversational analytics.

Snowflake, Databricks, Fabric, and BI tools now all support some form of natural language interaction.

This lowers the barrier to entry for analytics and reduces dependency on data teams for simple questions.

However, this only works well when:

  • Tables are properly named
  • Relationships are correct
  • Measures are clearly defined

Which brings us back to fundamentals.


3. Built-In AI Makes Advanced Analytics Easier

Power BI and Fabric now include:

  • Forecasting visuals
  • Anomaly detection
  • AutoML models
  • Cognitive services
  • Predictive features

What once required data scientists can often be done directly inside the platform.

This enables analysts to:

  • Add predictions to reports
  • Detect unusual behavior
  • Cluster customers
  • Score records

All without building custom ML pipelines.

Advanced analytics is becoming part of everyday BI.


4. AI Is Improving Developer Productivity

For analytics professionals, AI has become a daily productivity tool:

  • Writing DAX measures
  • Generating SQL
  • Creating Power Query transformations
  • Explaining model errors
  • Drafting documentation

Instead of searching forums or writing everything from scratch, teams use AI to accelerate development.

This is especially powerful for:

  • Junior analysts learning faster
  • Senior engineers moving quicker
  • Teams standardizing patterns

AI acts as an always-available assistant.


How AI Isn’t Changing Analytics

Despite all of this, Power BI projects (and analytics project in general) still succeed or fail for the same reasons they always have.


1. Data Modeling Still Drives Everything

Copilot can generate visuals.

It cannot fix a broken model.

If your Power BI semantic model has:

  • Poor relationships
  • Ambiguous dimensions
  • Duplicate metrics
  • Inconsistent grain

Your reports will still be confusing — no matter how much AI you add.

Star schemas, clear measures, and well-designed semantic layers remain essential.

AI works on top of your model. It does not replace it.


2. Data Quality Still Determines Trust

AI-powered insights mean nothing if the data is wrong.

If, for example:

  • Sales numbers don’t match Finance
  • Customer definitions vary by report
  • Dates behave inconsistently

Users will stop trusting dashboards.

Modern platforms like Fabric emphasize data pipelines, lakehouses, governance, and lineage for a reason.

Analytics still starts with reliable data engineering.


3. Metrics Still Require Human Agreement

Power BI can calculate anything.

AI can suggest formulas.

But only people can agree on:

  • What “revenue” means
  • How churn is defined
  • Which KPIs matter
  • What targets are realistic

Metric alignment remains a business process, not a technical one.

No AI can resolve organizational ambiguity.


4. Dashboards Don’t Drive Action — People Do

Smart narratives and AI summaries are useful.

But decisions still depend on:

  • Context
  • Priorities
  • Risk tolerance
  • Strategy

A Power BI report becomes valuable only when someone uses it to change behavior.

That requires storytelling, persuasion, and leadership — not just algorithms.


What This Means for Power BI and Analytics Professionals

AI is changing the workflow, not the purpose of analytics.

Less time spent on:

  • Boilerplate DAX
  • First-pass visuals
  • Manual exploration

More time spent on:

  • Understanding business problems
  • Designing models
  • Interpreting results
  • Influencing decisions

The role evolves from “report builder” to:

  • Analytics translator
  • Business partner
  • Insight driver

Power BI professionals who thrive will combine:

  • Strong modeling skills
  • Business understanding
  • Communication
  • Strategic thinking
  • AI-assisted productivity

The Bottom Line

Power BI and modern analytics platforms are becoming AI-powered.

But analytics is not becoming automatic.

AI accelerates:

  • Report creation
  • Exploration
  • Advanced analytics
  • Developer productivity

It does not replace:

  • Data modeling
  • Data quality
  • Business context
  • Metric alignment
  • Human judgment

AI amplifies good analytics practices — and exposes bad ones faster.

Organizations that succeed will be the ones that invest in:

  • Solid data foundations
  • Clear semantic models
  • Skilled analytics teams
  • Thoughtful AI adoption

Not just shiny features.


Thanks for reading and good luck on your data journey!

What Makes a Metric Actionable?

In data and analytics, not all metrics are created equal. Some look impressive on dashboards but don’t actually change behavior or decisions. Regardless of the domain, an actionable metric is one that clearly informs what to do next.

Here we outline a few guidelines for ensuring your metrics are actionable.

Clear and Well-Defined

An actionable metric has an unambiguous definition. Everyone understands:

  • What is being measured
  • How it’s calculated
  • What a “good” or “bad” value looks like

If stakeholders debate what the metric means, it has already lost its usefulness.

Tied to a Decision or Behavior

A metric becomes actionable when it supports a specific decision or action. You should be able to answer:
“If this number goes up or down, what will we do differently?”
If no action follows a change in the metric, it’s likely just informational, not actionable.

Within Someone’s Control

Actionable metrics measure outcomes that a team or individual can influence. For example:

  • Customer churn by product feature is more actionable than overall churn.
  • Query refresh failures by dataset owner is more actionable than total failures.

If no one can realistically affect the result, accountability disappears.

Timely and Frequent Enough

Metrics need to be available while action still matters. A perfectly accurate metric delivered too late is not actionable.

  • Operational metrics often need near-real-time or daily updates.
  • Strategic metrics may work on a weekly or monthly cadence.

The key is alignment with the decision cycle.

Contextual and Comparable

Actionable metrics provide context, such as:

  • Targets or thresholds
  • Trends over time
  • Comparisons to benchmarks or previous periods

A number without context raises questions; a number with context drives action.

Focused, Not Overloaded

Actionable metrics are usually simple and focused. When dashboards show too many metrics, attention gets diluted and action stalls. Fewer, well-chosen metrics lead to clearer priorities and faster responses.

Aligned to Business Goals

Finally, an actionable metric connects directly to a business objective. Whether the goal is improving customer experience, reducing costs, or increasing reliability, the metric should clearly support that outcome.


In Summary

A metric is actionable when it is clear, controllable, timely, contextual, and directly tied to a decision or goal. If a metric doesn’t change behavior or inform action, it may still be interesting—but it isn’t driving actionable value.
Good metrics don’t just describe the business. They help run it.

Thanks for reading and good luck on your data journey!

Power BI Drilldown vs. Drill-through: Understanding the Differences, Use Cases, and Setup

Power BI provides multiple ways to explore data interactively. Two of the most commonly confused features are drilldown and drill-through. While both allow users to move from high-level insights to more detailed data, they serve different purposes and behave differently.

This article explains what drilldown and drill-through are, when to use each, how to configure them, and how they compare.


What Is Drilldown in Power BI?

Drilldown allows users to navigate within the same visual to explore data at progressively lower levels of detail using a predefined hierarchy.

Key Characteristics

  • Happens inside a single visual
  • Uses hierarchies (date, geography, product, etc.)
  • Does not navigate to another page
  • Best for progressive exploration

Example

A column chart showing:

  • Year → Quarter → Month → Day
    A user clicks on 2024 to drill down into quarters, then into months.

Here is a short YouTube video on how to drilldown in a table visual.


When to Use Drilldown

Use drilldown when:

  • You want users to explore trends step by step
  • The data naturally follows a hierarchical structure
  • Context should remain within the same chart
  • You want a quick, visual breakdown

Typical use cases:

  • Time-based analysis (Year → Month → Day)
  • Sales by Category → Subcategory → Product
  • Geographic analysis (Country → State → City)

How to Set Up Drilldown

Step-by-Step

  1. Select a visual (bar chart, column chart, etc.)
  2. Drag multiple fields into the Axis (or equivalent) in hierarchical order
  3. Enable drill mode by clicking the Drill Down icon (↓) on the visual
  4. Interact with the visual:
    • Click a data point to drill
    • Use Drill Up to return to higher levels

Notes

  • Power BI auto-creates date hierarchies unless disabled
  • Drilldown works only when multiple hierarchy levels exist

Here is a YouTube video on how to set up hierarchies and drilldown in Power BI.


What Is Drill-through in Power BI?

Drill-through allows users to navigate from one report page to another page that shows detailed, filtered information based on a selected value.

Key Characteristics

  • Navigates to a different report page
  • Passes filters automatically
  • Designed for detailed analysis
  • Often uses dedicated detail pages

Example

From a summary sales page:

  • Right-click Product = Laptop
  • Drill through to a “Product Details” page
  • Page shows sales, margin, customers, and trends for Laptop only

When to Use Drill-through

Use drill-through when:

  • You need a separate, detailed view
  • The analysis requires multiple visuals
  • You want to preserve context via filters
  • Detail pages would clutter a summary page

Typical use cases:

  • Customer detail pages
  • Product performance analysis
  • Region- or department-specific deep dives
  • Incident or transaction-level reviews

How to Set Up Drill-through

Step-by-Step

  1. Create a new report page
  2. Add the desired detail visuals
  3. Drag one or more fields into the Drill-through filters pane
  4. (Optional) Add a Back button using:
    • Insert → Buttons → Back
  5. Test by right-clicking a data point on another page and selecting Drill through

Notes

  • Multiple fields can be passed
  • Works across visuals and tables
  • Requires right-click interaction (unless buttons are used)

Here is a short YouTube video on how to set up drill-through in Power BI

And here is a detailed YouTube video on creating a drill-through page in Power BI.


Drilldown vs. Drill-through: Key Differences

FeatureDrilldownDrill-through
NavigationSame visualDifferent page
Uses hierarchiesYesNo (uses filters)
Page changeNoYes
Level of detailIncrementalComprehensive
Typical useTrend explorationDetailed analysis
User interactionClickRight-click or button

Similarities Between Drilldown and Drill-through

Despite their differences, both features:

  • Enhance interactive data exploration
  • Preserve user context
  • Reduce report clutter
  • Improve self-service analytics
  • Work with Power BI visuals and filters

Common Pitfalls and Best Practices

Best Practices

  • Use drilldown for simple, hierarchical exploration
  • Use drill-through for rich, detailed analysis
  • Clearly label drill-through pages
  • Add Back buttons for usability
  • Avoid overloading a single visual with too many drill levels

Common Mistakes

  • Using drilldown when a detail page is needed
  • Forgetting to configure drill-through filters
  • Hiding drill-through functionality from users
  • Mixing drilldown and drill-through without clear design intent

Summary

  • Drilldown = explore deeper within the same visual
  • Drill-through = navigate to a dedicated detail page
  • Drilldown is best for hierarchies and trends
  • Drill-through is best for focused, detailed analysis

Understanding when and how to use each feature is essential for building intuitive, powerful Power BI reports—and it’s a common topic tested in Power BI certification exams.

Thanks for reading and good luck on your data journey!

Metrics vs KPIs: What’s the Difference?

The terms metrics and KPIs (Key Performance Indicators) are often used interchangeably, but they are not the same thing. Understanding the difference helps teams focus on what truly matters instead of tracking everything.


What Is a Metric?

A metric is any quantitative measure used to track an activity, process, or outcome. Metrics answer the question:

“What is happening?”

Examples of metrics include:

  • Number of website visits
  • Average query duration
  • Support tickets created per day
  • Data refresh success rate

Metrics are abundant and valuable. They provide visibility into operations and performance, but on their own, they don’t always indicate success or failure.


What Is a KPI?

A KPI (Key Performance Indicator) is a specific type of metric that is directly tied to a strategic business objective. KPIs answer the question:

“Are we succeeding at what matters most?”

Examples of KPIs include:

  • Customer retention rate
  • Revenue growth
  • On-time data availability SLA
  • Net Promoter Score (NPS)

A KPI is not just measured—it is monitored, discussed, and acted upon at a leadership or decision-making level.


The Key Differences

Purpose

  • Metrics provide insight and detail.
  • KPIs track progress toward critical goals.

Scope

  • Metrics are broad and numerous.
  • KPIs are few and highly focused.

Audience

  • Metrics are often used by analysts and operational teams.
  • KPIs are used by leadership and decision-makers.

Actionability

  • Metrics may or may not drive action.
  • KPIs are designed to trigger decisions and accountability.

How Metrics Support KPIs

KPIs rarely exist in isolation. They are usually supported by multiple underlying metrics. For example:

  • A customer retention KPI may be supported by metrics such as churn by segment, feature usage, and support response time.
  • A data platform reliability KPI may rely on refresh failures, latency, and incident counts.

Metrics provide the diagnostic detail; KPIs provide the direction.


Common Mistakes to Avoid

  • Too many KPIs: When everything is “key,” nothing is.
  • Unowned KPIs: Every KPI should have a clear owner responsible for outcomes.
  • Vanity KPIs: A KPI should drive action, not just look good in reports.
  • Misaligned KPIs: If a KPI doesn’t clearly map to a business goal, it shouldn’t be a KPI.

When to Use Each

Use metrics to understand, analyze, and optimize processes.
Use KPIs to evaluate success, guide priorities, and align teams around shared goals.


In Summary

All KPIs are metrics, but not all metrics are KPIs. Metrics tell the story of what’s happening across the business, while KPIs highlight the chapters that truly matter. Strong analytics practices use both—metrics for insight and KPIs for focus.

Thanks for reading and good luck on your data journey!

Glossary – 100 “Data Visualization” Terms

Below is a glossary that includes 100 common “Data Visualization” terms and phrases in alphabetical order. Enjoy!

TermDefinition & Example
 AccessibilityDesigning for all users. Example: Colorblind-friendly palette.
 AggregationSummarizing data. Example: Sum of sales.
 AlignmentProper positioning of elements. Example: Grid layout.
 AnnotationExplanatory text on a visual. Example: Highlighting a spike.
 Area ChartLine chart with filled area. Example: Cumulative sales.
 AxisReference line for measurement. Example: X and Y axes.
 Bar ChartUses bars to compare categories. Example: Sales by product.
 BaselineReference starting point. Example: Zero line.
 Best PracticeRecommended visualization approach. Example: Avoid 3D charts.
 BinningGrouping continuous values. Example: Age ranges.
 Box PlotDisplays data distribution and outliers. Example: Salary ranges.
 Bubble ChartScatter plot with size dimension. Example: Profit by region and size.
 CardDisplays a single value. Example: Total customers.
 Categorical ScaleDiscrete category scale. Example: Product names.
 ChartVisual representation of data values. Example: Bar chart of revenue by region.
 Chart JunkUnnecessary visual elements. Example: Excessive shadows.
 Choropleth MapMap colored by value. Example: Sales by state.
 Cognitive LoadMental effort required to interpret. Example: Overly complex charts.
 Color EncodingUsing color to represent data. Example: Red for losses.
 Color PaletteSelected set of colors. Example: Brand colors.
 Column ChartVertical bar chart. Example: Revenue by year.
 Comparative AnalysisComparing values. Example: Year-over-year sales.
 Conditional FormattingFormatting based on values. Example: Red for negative.
 ContextSupporting information for visuals. Example: Benchmarks.
 Continuous ScaleNumeric scale without breaks. Example: Temperature.
 CorrelationRelationship between variables. Example: Scatter plot trend.
 DashboardCollection of visualizations on one screen. Example: Executive KPI dashboard.
 Dashboard LayoutArrangement of visuals. Example: Top-down flow.
 Data DensityAmount of data per visual area. Example: Dense scatter plot.
 Data Ink RatioProportion of ink used for data. Example: Minimal chart clutter.
 Data RefreshUpdating visualized data. Example: Daily refresh.
 Data StoryStructured insight narrative. Example: Executive presentation.
 Data VisualizationGraphical representation of data. Example: Sales trends shown in a line chart.
 Data-to-Ink RatioProportion of ink showing data. Example: Minimalist charts.
 Density PlotSmoothed distribution visualization. Example: Probability density.
 DistributionSpread of data values. Example: Histogram shape.
 Diverging ChartShows deviation from a baseline. Example: Profit vs target.
 Diverging PaletteColors diverging from midpoint. Example: Profit/loss.
 Donut ChartPie chart with a center hole. Example: Expense breakdown.
 Drill DownNavigating to more detail. Example: Year → month → day.
 Drill ThroughNavigating to a detailed report. Example: Customer detail page.
 Dual Axis ChartTwo measures on different axes. Example: Sales and margin.
 EmphasisDrawing attention to key data. Example: Bold colors.
 Explanatory VisualizationUsed to communicate findings. Example: Board presentation.
 Exploratory VisualizationUsed to discover insights. Example: Ad-hoc analysis.
 FacetingSplitting data into subplots. Example: One chart per category.
 FilteringLimiting displayed data. Example: Filter by year.
 FootnoteAdditional explanation text. Example: Data source note.
 ForecastPredicted future values. Example: Next quarter sales.
 Funnel ChartShows process stages. Example: Sales pipeline.
 GaugeDisplays progress toward a target. Example: KPI completion.
 Geospatial VisualizationData mapped to geography. Example: Customer density map.
 GranularityLevel of data detail. Example: Daily vs monthly.
 GraphDiagram showing relationships between variables. Example: Scatter plot of height vs weight.
 GroupingCombining similar values. Example: Products by category.
 HeatmapUses color to show intensity. Example: Sales by day and hour.
 HierarchyParent-child relationships. Example: Country → State → City.
 HighlightingEmphasizing specific data. Example: Selected bar.
 HistogramDistribution of numerical data. Example: Customer age distribution.
 InsightMeaningful takeaway from data. Example: Sales decline identified.
 InteractivityUser-driven exploration. Example: Click to filter.
 KPI VisualHighlights key performance metrics. Example: Total revenue card.
 LabelText identifying data points. Example: Value labels on bars.
 LegendExplains colors or symbols. Example: Product categories.
 Legend PlacementPosition of legend. Example: Right side.
 Line ChartShows trends over time. Example: Daily website traffic.
 MatrixTable with grouped dimensions. Example: Sales by region and year.
 OutlierValue far from others. Example: Extremely high sales.
 PanMove across a visual. Example: Map navigation.
 Pie ChartDisplays parts of a whole. Example: Market share.
 ProportionPart-to-whole relationship. Example: Market share.
 RankingDisplaying relative position. Example: Top 10 customers.
 Real-Time VisualizationLive data display. Example: Streaming metrics.
 Reference LineBenchmark line on chart. Example: Target line.
 ReportStructured set of visuals and text. Example: Monthly performance report.
 Responsive DesignAdjusts to screen size. Example: Mobile dashboards.
 Scatter PlotShows relationship between two variables. Example: Ad spend vs revenue.
 Sequential PaletteGradual color progression. Example: Low to high values.
 Shape EncodingUsing shapes to distinguish categories. Example: Circles vs triangles.
 Size EncodingUsing size to represent values. Example: Bubble size.
 SlicerInteractive filter control. Example: Dropdown region selector.
 Small MultiplesSeries of similar charts. Example: Sales by region panels.
 SortingOrdering data values. Example: Top-selling products.
 StorytellingCommunicating insights visually. Example: Narrative dashboard.
To learn more, check out this article on Data Storytelling.
 SubtitleSupporting chart description. Example: Fiscal year context.
 Symbol MapMap using symbols. Example: Store locations.
 TableData displayed in rows and columns. Example: Transaction list.
 TitleDescriptive chart heading. Example: “Monthly Sales Trend.”
 TooltipHover text showing details. Example: Exact value on hover.
 TreemapHierarchical data using rectangles. Example: Revenue by category.
 TrendlineShows overall direction. Example: Sales trend.
 Visual ClutterOvercrowded visuals. Example: Too many labels.
 Visual ConsistencyUniform styling across visuals. Example: Same fonts/colors.
 Visual EncodingMapping data to visuals. Example: Color = category.
 Visual HierarchyOrdering elements by importance. Example: Large KPI at top.
 Waterfall ChartShows cumulative effect of changes. Example: Profit bridge analysis.
 White SpaceEmpty space improving readability. Example: Padding between charts.
 X-AxisHorizontal axis. Example: Time dimension.
 Y-AxisVertical axis. Example: Sales amount.
 ZoomFocus on specific area. Example: Map zoom.