Category: Data Modeling

Analytics, Business Intelligence, Data Modeling, DP-900, Microsoft Certification, Power BI, Power Query May 10, 2026

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

Load data into Power BI
Clean and transform data (Power Query)
Define relationships
Create measures and calculations
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.

Data Development, Data Education & Training, Data Modeling, Databases, DP-900, SQL, Uncategorized May 10, 2026

Identify common Structured Query Language (SQL) statements (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:
Identify considerations for relational data on Azure (20–25%)
   --> Describe relational concepts
      --> Identify common Structured Query Language (SQL) statements

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.

Understanding basic SQL statements is essential for working with relational data and is a key requirement for the DP-900 exam. You are not expected to be an advanced SQL developer, but you should recognize common SQL commands, their purpose, and when they are used.

What Is SQL?

Structured Query Language (SQL) is the standard language used to:

Query data
Insert new data
Update existing data
Delete data
Define database structures

SQL is used across relational database systems, including Azure services like:

Azure SQL Database
Azure Database for PostgreSQL
Azure Database for MySQL

Categories of SQL Statements

SQL statements are typically grouped into categories:

Category	Purpose
DDL (Data Definition Language)	Define and modify database structures
DML (Data Manipulation Language)	Work with data in tables
DQL (Data Query Language)	Retrieve data
DCL (Data Control Language)	Manage permissions

For DP-900, focus primarily on DDL, DML, and DQL.

1. Data Query Language (DQL)

SELECT

Used to retrieve data from a table.

			
SELECT Name, City
FROM Customers;

You can filter results:

			
SELECT Name
FROM Customers
WHERE City = 'Seattle';

💡 Key Points:

Most commonly used SQL statement
Can include filtering, sorting, and grouping

2. Data Manipulation Language (DML)

INSERT

Adds new rows to a table.

			
INSERT INTO Customers (Name, City)
VALUES ('John', 'Seattle');

UPDATE

Modifies existing data.

			
UPDATE Customers
SET City = 'Austin'
WHERE Name = 'John';

DELETE

Removes rows from a table.

			
DELETE FROM Customers
WHERE Name = 'John';

💡 Important:
Always use a WHERE clause with UPDATE and DELETE to avoid affecting all rows.

3. Data Definition Language (DDL)

CREATE

Creates new database objects such as tables.

			
CREATE TABLE Customers (
    CustomerID INT PRIMARY KEY,
    Name VARCHAR(100),
    City VARCHAR(50)
);

		

ALTER

Modifies an existing table.

			
ALTER TABLE Customers
ADD Email VARCHAR(100);

DROP

Deletes a table or database object.

DROP TABLE Customers;

💡 Warning:
DROP permanently removes the object and its data.

4. Additional Common SQL Clauses

WHERE

Filters rows:

			
SELECT * FROM Orders
WHERE Amount > 100;

ORDER BY

Sorts results:

			
SELECT * FROM Orders
ORDER BY Amount DESC;

GROUP BY

Aggregates data:

			
SELECT City, COUNT(*)
FROM Customers
GROUP BY City;

JOIN

Combines data from multiple tables:

			
SELECT Orders.OrderID, Customers.Name
FROM Orders
JOIN Customers
ON Orders.CustomerID = Customers.CustomerID;

💡 DP-900 Tip:
You don’t need deep JOIN knowledge — just understand that JOINs combine related tables.

SQL in Azure

SQL is used across many Azure services:

Azure SQL Database

Fully managed relational database
Uses T-SQL (Microsoft’s SQL variant)

Azure Synapse Analytics

Used for analytical queries on large datasets

Azure Database for PostgreSQL

Uses PostgreSQL SQL dialect

Why This Matters for DP-900

On the exam, you may be asked to:

Identify what a SQL statement does
Match commands to their purpose (SELECT, INSERT, etc.)
Recognize DDL vs DML
Understand basic query concepts like filtering and sorting

Summary — Exam-Relevant Takeaways

✔ SELECT → Retrieve data
✔ INSERT → Add new data
✔ UPDATE → Modify existing data
✔ DELETE → Remove data

✔ CREATE / ALTER / DROP → Define and modify structures
✔ WHERE → Filter results
✔ ORDER BY → Sort data
✔ GROUP BY → Aggregate data
✔ JOIN → Combine tables

✔ SQL is the standard language for relational databases

Go to the Practice Exam Questions for this topic.

Go to the Additional Practice Questions for this topic.

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

Data Modeling, Databases, DP-900, Microsoft Certification May 10, 2026

Describe normalization and why it is used (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:
Identify considerations for relational data on Azure (20–25%)
   --> Describe relational concepts
      --> Describe normalization and why it is used

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.

Normalization is a foundational concept in relational database design. For the DP-900 exam, you are expected to understand what normalization is, why it is important, and how it improves data quality and efficiency.

What Is Normalization?

Normalization is the process of organizing data in a relational database to:

Reduce data redundancy (duplicate data)
Improve data integrity
Ensure logical data relationships

This is done by splitting data into multiple related tables and defining relationships between them using keys.

Why Normalization Is Used

Normalization is used to solve common data problems in poorly designed tables.

1. Reduce Data Redundancy

Without normalization, the same data may be repeated across multiple rows.

Example (Unnormalized Table):

OrderID	CustomerName	CustomerCity	Product
1	John	Seattle	Laptop
2	John	Seattle	Mouse

Here, customer information is duplicated.

After Normalization:

Customers Table

CustomerID	Name	City
1	John	Seattle

Orders Table

OrderID	CustomerID	Product
1	1	Laptop
2	1	Mouse

Now, customer data is stored once and referenced using a key.

2. Improve Data Integrity

Normalization ensures that data remains accurate and consistent.

Without normalization:

Updating a customer’s city requires changing multiple rows
Missing one update leads to inconsistent data

With normalization:

Data is updated in one place only
Consistency is maintained automatically

3. Prevent Data Anomalies

Normalization helps prevent common issues:

Insert anomaly: Cannot add data without unrelated data
Update anomaly: Inconsistent updates across rows
Delete anomaly: Deleting one record removes important data

Normalized designs eliminate these problems.

4. Improve Data Organization

Normalized databases:

Clearly separate different entities (customers, orders, products)
Use relationships to connect data logically
Make databases easier to maintain and scale

Understanding Normal Forms (Simplified for DP-900)

Normalization is often described in stages called normal forms. For DP-900, you only need a basic understanding:

First Normal Form (1NF)

No repeating groups or multi-valued fields
Each column contains atomic (single) values

Second Normal Form (2NF)

Meets 1NF
All non-key columns depend on the entire primary key

Third Normal Form (3NF)

Meets 2NF
No dependency between non-key columns

💡 DP-900 Tip:
You do NOT need to memorize formal definitions — just understand that normalization reduces redundancy and improves integrity.

Trade-Offs of Normalization

While normalization has many benefits, there are trade-offs:

Advantages

✔ Reduces duplicate data
✔ Improves consistency
✔ Simplifies updates
✔ Enhances data integrity

Disadvantages

✖ Requires more tables
✖ Queries may require joins
✖ Can slightly impact performance for complex queries

Normalization vs Denormalization

Understanding this comparison is important for the exam:

Feature	Normalization	Denormalization
Data Redundancy	Reduced	Increased
Data Integrity	High	Lower
Query Complexity	Higher (joins required)	Lower
Performance	Slower for reads	Faster for analytics
Use Case	Transactional systems (OLTP)	Analytical systems (OLAP)

Where Normalization Is Used in Azure

Normalization is commonly applied in relational database services such as:

Azure SQL Database
Azure Database for PostgreSQL
Azure Database for MySQL

These services are typically used for transactional workloads, where data integrity is critical.

Why This Matters for DP-900

On the exam, you may be asked to:

Identify why normalization is used
Recognize normalized vs unnormalized structures
Understand how normalization affects data integrity
Distinguish normalization from denormalization

Summary — Exam-Relevant Takeaways

✔ Normalization organizes data into multiple related tables
✔ It reduces data redundancy
✔ It improves data integrity and consistency
✔ It prevents insert, update, and delete anomalies
✔ It is commonly used in transactional (OLTP) systems
✔ It may require joins when querying data

Go to the Practice Exam Questions for this topic.

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

Data Modeling, DP-900, Microsoft Certification May 10, 2026

Practice Questions: Describe normalization and why it is used (DP-900 Exam Prep)

Practice Questions

Question 1

What is the primary purpose of normalization in a relational database?

A. Increase data duplication
B. Improve query speed for analytics
C. Reduce data redundancy and improve integrity
D. Store unstructured data

✅ Answer: C

Explanation:
Normalization reduces duplicate data and improves consistency and integrity.

Question 2

Which issue is MOST likely to occur in a non-normalized table?

A. Faster query performance
B. Data redundancy
C. Reduced storage requirements
D. Simpler queries

✅ Answer: B

Explanation:
Without normalization, the same data is often stored multiple times.

Question 3

A database stores customer details repeatedly in every order record. What problem does normalization solve in this scenario?

A. Improves indexing
B. Reduces redundancy
C. Enhances encryption
D. Increases data size

✅ Answer: B

Explanation:
Normalization separates customer data into its own table to avoid duplication.

Question 4

Which anomaly occurs when updating the same data in multiple rows leads to inconsistent values?

A. Insert anomaly
B. Delete anomaly
C. Update anomaly
D. Query anomaly

✅ Answer: C

Explanation:
Update anomalies happen when duplicate data is not consistently updated.

Question 5

Which approach is commonly used in normalized database design?

A. Storing all data in a single table
B. Splitting data into related tables
C. Removing all relationships between data
D. Using only unstructured formats

✅ Answer: B

Explanation:
Normalization divides data into multiple related tables.

Question 6

Which statement best describes First Normal Form (1NF)?

A. Data must be encrypted
B. Tables must include foreign keys
C. Each column contains atomic (single) values
D. Tables must be denormalized

✅ Answer: C

Explanation:
1NF requires that each field contains indivisible values and no repeating groups.

Question 7

What is a trade-off of normalization?

A. Increased data redundancy
B. Simpler queries with no joins
C. More complex queries due to joins
D. Reduced data integrity

✅ Answer: C

Explanation:
Normalized databases often require joins, making queries more complex.

Question 8

Which type of workload benefits MOST from normalized data?

A. Analytical workloads
B. Transactional workloads
C. Streaming workloads
D. Machine learning workloads

✅ Answer: B

Explanation:
Transactional systems prioritize data integrity, which normalization supports.

Question 9

Which action is an example of normalization?

A. Combining multiple tables into one
B. Storing duplicate data for faster reads
C. Separating customer and order data into different tables
D. Removing relationships between tables

✅ Answer: C

Explanation:
Normalization separates data into logical entities and links them via keys.

Question 10

Why might a system choose denormalization instead of normalization?

A. To improve data integrity
B. To reduce redundancy
C. To improve read performance for analytics
D. To enforce strict schemas

✅ Answer: C

Explanation:
Denormalization is often used in analytical systems to improve query performance.

✅ Quick Exam Takeaways

For DP-900, remember:

✔ Normalization = reduce redundancy + improve integrity
✔ Involves splitting data into related tables
✔ Prevents:

Insert anomalies
Update anomalies
Delete anomalies

✔ Used primarily in transactional (OLTP) systems
✔ Trade-off = more joins / more complex queries
✔ Opposite concept = denormalization (used in analytics)

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

Data Modeling, Databases, DP-900, Microsoft Certification, SQL May 10, 2026

Identify features of relational data (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:
Identify considerations for relational data on Azure (20–25%)
   --> Describe relational concepts
      --> Identify features of relational data

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.

Relational data is one of the most fundamental concepts in data management and a core focus area for the DP-900 exam. Understanding how relational data is structured, stored, and accessed will help you confidently answer questions related to databases, querying, and Azure data services.

What Is Relational Data?

Relational data is data that is organized into tables (relations) consisting of:

Rows (records)
Columns (attributes or fields)

Each table represents a specific entity, such as customers, orders, or products. Relationships between tables are defined using keys.

Core Features of Relational Data

1. Tabular Structure (Rows and Columns)

Relational data is stored in a structured, tabular format:

Each row represents a single record
Each column represents a specific attribute

Example:

CustomerID	Name	City
1	John	Seattle
2	Maria	Austin

This structure makes relational data easy to query and understand.

2. Predefined Schema

Relational databases enforce a fixed schema, which defines:

Table structure
Column names
Data types (e.g., INT, VARCHAR, DATE)

This ensures:

Data consistency
Data validation
Predictable structure

3. Use of Keys

Keys are essential for uniquely identifying records and linking tables.

Primary Key

Uniquely identifies each row in a table
Cannot contain duplicate or null values

Example: CustomerID

Foreign Key

Links one table to another
Establishes relationships between tables

Example: Order.CustomerID → Customer.CustomerID

4. Relationships Between Tables

Relational data supports relationships such as:

One-to-One
One-to-Many
Many-to-Many

Example:

One customer can have many orders (one-to-many)

These relationships allow complex data models to be built efficiently.

5. Structured Query Language (SQL)

Relational data is accessed and manipulated using Structured Query Language (SQL).

SQL is used to:

Query data (SELECT)
Insert data (INSERT)
Update data (UPDATE)
Delete data (DELETE)

Example:

SELECT Name FROM Customers WHERE City = 'Seattle';

6. Data Integrity and Constraints

Relational databases enforce data integrity through constraints such as:

PRIMARY KEY
FOREIGN KEY
NOT NULL
UNIQUE
CHECK

These rules ensure that:

Data is accurate
Relationships remain valid
Invalid data is prevented

7. Normalization

Relational data is often normalized to reduce redundancy and improve consistency.

Normalization involves:

Splitting data into multiple related tables
Eliminating duplicate data
Ensuring dependencies are logical

Example:

Instead of storing customer details in every order row, store them in a separate Customers table.

8. ACID Transactions

Relational databases support ACID properties, ensuring reliable transactions:

Atomicity → All or nothing
Consistency → Valid state maintained
Isolation → Transactions don’t interfere
Durability → Changes persist

This is especially important for transactional workloads.

Relational Data in Azure

Azure provides several services for working with relational data:

Azure SQL Database

Fully managed relational database
Supports SQL queries
High availability and scalability
Ideal for OLTP applications

Azure Database for PostgreSQL

Managed open-source relational database
Supports PostgreSQL features and extensions

Azure Database for MySQL

Managed MySQL database service
Suitable for web and application workloads

These services support structured data, relationships, and SQL-based querying.

Why This Matters for DP-900

On the exam, you may be asked to:

Identify characteristics of relational data
Recognize table-based structures
Understand keys and relationships
Distinguish relational data from non-relational data
Match relational workloads to Azure services

Summary — Exam-Relevant Takeaways

✔ Relational data is stored in tables (rows and columns)
✔ It uses a fixed schema with defined data types
✔ Primary and foreign keys define relationships
✔ Data is accessed using SQL
✔ Supports data integrity constraints
✔ Often normalized to reduce redundancy
✔ Ensures reliability with ACID transactions

✔ Common Azure services:

Azure SQL Database
Azure Database for PostgreSQL
Azure Database for MySQL

Go to the Practice Exam Questions for this topic.

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

Data Modeling, Databases, DP-900, Microsoft Certification May 10, 2026

Practice Questions: Identify features of relational data (DP-900 Exam Prep)

Practice Questions

Question 1

Which structure is used to store relational data?

A. Key-value pairs
B. Graph nodes and edges
C. Tables with rows and columns
D. JSON documents

✅ Answer: C

Explanation:
Relational data is organized in tables consisting of rows and columns.

Question 2

What is the purpose of a primary key in a relational table?

A. To link tables together
B. To uniquely identify each row
C. To store duplicate values
D. To define column data types

✅ Answer: B

Explanation:
A primary key uniquely identifies each record and cannot contain duplicates or null values.

Question 3

Which element is used to create relationships between tables?

A. Index
B. Column constraint
C. Foreign key
D. Schema

✅ Answer: C

Explanation:
A foreign key links one table to another by referencing a primary key.

Question 4

Which statement best describes a schema in a relational database?

A. A collection of unstructured files
B. A visual report of data
C. The structure defining tables, columns, and data types
D. A backup of the database

✅ Answer: C

Explanation:
A schema defines how data is structured, including tables, columns, and data types.

Question 5

Which language is used to query relational databases?

A. Python
B. JSON
C. SQL
D. HTML

✅ Answer: C

Explanation:
Structured Query Language (SQL) is used to query and manage relational data.

Question 6

Which constraint ensures that a column cannot contain null values?

A. UNIQUE
B. CHECK
C. NOT NULL
D. FOREIGN KEY

✅ Answer: C

Explanation:
The NOT NULL constraint ensures that a value must be provided for that column.

Question 7

Which concept reduces data redundancy by organizing data into multiple related tables?

A. Indexing
B. Normalization
C. Partitioning
D. Replication

✅ Answer: B

Explanation:
Normalization reduces redundancy and improves data integrity.

Question 8

Which type of relationship allows one record in a table to relate to many records in another table?

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

✅ Answer: B

Explanation:
One-to-many relationships are common in relational databases (e.g., one customer → many orders).

Question 9

Which property ensures that all parts of a transaction succeed or fail together?

A. Consistency
B. Isolation
C. Atomicity
D. Durability

✅ Answer: C

Explanation:
Atomicity ensures transactions are completed fully or not at all.

Question 10

Which Azure service is specifically designed for relational data?

A. Azure Blob Storage
B. Azure Cosmos DB
C. Azure SQL Database
D. Azure Data Lake Storage

✅ Answer: C

Explanation:
Azure SQL Database is a fully managed relational database service.

✅ Quick Exam Takeaways

For DP-900, remember:

✔ Relational data = tables (rows + columns)
✔ Schema defines structure
✔ Primary keys uniquely identify rows
✔ Foreign keys create relationships
✔ Use SQL for querying
✔ Constraints enforce data integrity
✔ Normalization reduces redundancy
✔ Supports ACID transactions

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

Business Intelligence (BI) Development, Data Modeling, Power BI March 22, 2026

How to delete multiple fields (including measures) at the same time in Power BI

You find that you need to delete many fields (which can include measures) from a Power BI model / project, such as after removing a part of the solution that is no longer needed or will not be a part of the current release.

From the “Report View”, you can delete only one field at a time. However, you can delete multiple at a time from the “Model View”.

In your Power BI report, click the “Model View” in the left navigation pane.

Then, in the Data pane on the right, hold down the Ctrl key and click on each of the field that you want to delete.

All the fields you clicked on will be “selected” and you should see that they are.

Then, click the Delete key -or- right-click the fields and select “Delete from model”.

A “Delete items” confirmation dialog will pop up. After confirming that you have selected the fields you really want to delete, click “Yes”, or click “Cancel” to cancel your action.

Good luck!

Analytics, Business Intelligence, Data Analysis, Data Modeling, Data Visualization, Power BI January 25, 2026January 25, 2026

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

Select a visual (bar chart, column chart, etc.)
Drag multiple fields into the Axis (or equivalent) in hierarchical order
Enable drill mode by clicking the Drill Down icon (↓) on the visual
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

Create a new report page
Add the desired detail visuals
Drag one or more fields into the Drill-through filters pane
(Optional) Add a Back button using:
- Insert → Buttons → Back
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

Feature	Drilldown	Drill-through
Navigation	Same visual	Different page
Uses hierarchies	Yes	No (uses filters)
Page change	No	Yes
Level of detail	Incremental	Comprehensive
Typical use	Trend exploration	Detailed analysis
User interaction	Click	Right-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!

Analytics, Business Intelligence, Data Cleaning, Data Development, Data Governance, Data Integration, Data Modeling, Data Quality Assurance, Data Security, Data Strategy, Data Visualization January 22, 2026

Self-Service Analytics: Empowering Users While Maintaining Trust and Control

Self-service analytics has become a cornerstone of modern data strategies. As organizations generate more data and business users demand faster insights, relying solely on centralized analytics teams creates bottlenecks. Self-service analytics shifts part of the analytical workload closer to the business—while still requiring strong foundations in data quality, governance, and enablement.

This article is based on a detailed presentation I did at a HIUG conference a few years ago.

What Is Self-Service Analytics?

Self-service analytics refers to the ability for business users—such as analysts, managers, and operational teams—to access, explore, analyze, and visualize data on their own, without requiring constant involvement from IT or centralized data teams.

Instead of submitting requests and waiting days or weeks for reports, users can:

Explore curated datasets
Build their own dashboards and reports
Answer ad-hoc questions in real time
Make data-driven decisions within their daily workflows

Self-service does not mean unmanaged or uncontrolled analytics. Successful self-service environments combine user autonomy with governed, trusted data and clear usage standards.

Why Implement or Provide Self-Service Analytics?

Organizations adopt self-service analytics to address speed, scalability, and empowerment challenges.

Key Benefits

Faster Decision-Making
Users can answer questions immediately instead of waiting in a reporting queue.
Reduced Bottlenecks for Data Teams
Central teams spend less time producing basic reports and more time on high-value work such as modeling, optimization, and advanced analytics.
Greater Business Engagement with Data
When users interact directly with data, data literacy improves and analytics becomes part of everyday decision-making.
Scalability
A small analytics team cannot serve hundreds or thousands of users manually. Self-service scales insight generation across the organization.
Better Alignment with Business Context
Business users understand their domain best and can explore data with that context in mind, uncovering insights that might otherwise be missed.

Why Not Implement Self-Service Analytics? (Challenges & Risks)

While powerful, self-service analytics introduces real risks if implemented poorly.

Common Challenges

Data Inconsistency & Conflicting Metrics
Without shared definitions, different users may calculate the same KPI differently, eroding trust.
“Spreadsheet Chaos” at Scale
Self-service without governance can recreate the same problems seen with uncontrolled Excel usage—just in dashboards.
Overloaded or Misleading Visuals
Users may build reports that look impressive but lead to incorrect conclusions due to poor data modeling or statistical misunderstandings.
Security & Privacy Risks
Improper access controls can expose sensitive or regulated data.
Low Adoption or Misuse
Without training and support, users may feel overwhelmed or misuse tools, resulting in poor outcomes.
Shadow IT
If official self-service tools are too restrictive or confusing, users may turn to unsanctioned tools and data sources.

**What an Environment Looks Like Without Self-Service Analytics**

In organizations without self-service analytics, patterns tend to repeat:

Business users submit report requests via tickets or emails
Long backlogs form for even simple questions
Analytics teams become report factories
Insights arrive too late to influence decisions
Users create their own disconnected spreadsheets and extracts
Trust in data erodes due to multiple versions of the truth

Decision-making becomes reactive, slow, and often based on partial or outdated information.

**How Things Change With Self-Service Analytics**

When implemented well, self-service analytics fundamentally changes how an organization works with data.

Users explore trusted datasets independently
Analytics teams focus on enablement, modeling, and governance
Insights are discovered earlier in the decision cycle
Collaboration improves through shared dashboards and metrics
Data becomes part of daily conversations, not just monthly reports

The organization shifts from report consumption to insight exploration. Well, that’s the goal.

How to Implement Self-Service Analytics Successfully

Self-service analytics is as much an operating model as it is a technology choice. The list below outlines important aspects that must be considered, decided on, and implemented when planning the implementation of self-service analytics.

1. Data Foundation

Curated, well-modeled datasets (often star schemas or semantic models)
Clear metric definitions and business logic
Certified or “gold” datasets for common use cases
Data freshness aligned with business needs

A strong semantic layer is critical—users should not have to interpret raw tables.

2. Processes

Defined workflows for dataset creation and certification
Clear ownership for data products and metrics
Feedback loops for users to request improvements or flag issues
Change management processes for metric updates

3. Security

Role-based access control (RBAC)
Row-level and column-level security where needed
Separation between sensitive and general-purpose datasets
Audit logging and monitoring of usage

Security must be embedded, not bolted on.

4. Users & Roles

Successful self-service environments recognize different user personas:

Consumers: View and interact with dashboards
Explorers: Build their own reports from curated data
Power Users: Create shared datasets and advanced models
Data Teams: Govern, enable, and support the ecosystem

Not everyone needs the same level of access or capability.

5. Training & Enablement

Tool-specific training (e.g., how to build reports correctly)
Data literacy education (interpreting metrics, avoiding bias)
Best practices for visualization and storytelling
Office hours, communities of practice, and internal champions

Training is ongoing—not a one-time event.

6. Documentation

Metric definitions and business glossaries
Dataset descriptions and usage guidelines
Known limitations and caveats
Examples of certified reports and dashboards

Good documentation builds trust and reduces rework.

7. Data Governance

Self-service requires guardrails, not gates.

Key governance elements include:

Data ownership and stewardship
Certification and endorsement processes
Naming conventions and standards
Quality checks and validation
Policies for personal vs shared content

Governance should enable speed while protecting consistency and trust.

8. Technology & Tools

Modern self-service analytics typically includes:

Data Platforms

Cloud data warehouses or lakehouses
Centralized semantic models

Data Visualization & BI Tools

Interactive dashboards and ad-hoc analysis
Low-code or no-code report creation
Sharing and collaboration features

Supporting Capabilities

Metadata management
Cataloging and discovery
Usage monitoring and adoption analytics

The key is selecting tools that balance ease of use with enterprise-grade governance.

Conclusion

Self-service analytics is not about giving everyone raw data and hoping for the best. It is about empowering users with trusted, governed, and well-designed data experiences.

Organizations that succeed treat self-service analytics as a partnership between data teams and the business—combining strong foundations, thoughtful governance, and continuous enablement. When done right, self-service analytics accelerates decision-making, scales insight creation, and embeds data into the fabric of everyday work.

Thanks for reading!

Data Integration, Data Modeling, Power BI January 18, 2026

How to turn off “Autodetect New Relationships” in Power BI (and why you may consider doing it)

Power BI includes a feature called Autodetect new relationships that automatically creates relationships between tables when new data is loaded into a model. While convenient for simple datasets, this setting can cause unexpected behavior in more advanced data models.

How to Turn Off Autodetect New Relationships

You can disable this feature directly from Power BI Desktop:

Open Power BI Desktop
Go to File → Options and settings → Options
In the left pane, under CURRENT FILE, select Data Load
Then in the page’s main area, under the Relationships section, uncheck:
- Autodetect new relationships after data is loaded
Click OK

Note that you may need to refresh your model for the change to fully take effect on newly loaded data.

Why You May Want to Disable This Feature

Turning off automatic relationship detection is considered a best practice for many professional Power BI models, especially as complexity increases.

Key reasons to disable it include:

Prevent unintended relationships
This is the main reason. Power BI may create relationships you did not intend, based solely on matching column names or data types. Automatically generated relationships can introduce ambiguity and inactive relationships, leading to incorrect DAX results or performance issues.
Maintain full control of the data model, especially when the model needs to be carefully designed because of complexity or other reasons
Manually creating relationships ensures they follow your star schema design and business logic. Complex models with role-playing dimensions, bridge tables, or composite models benefit from intentional, not automatic, relationships.
Improve model reliability and maintainability
Explicit relationships make your model easier to understand, document, and troubleshoot.

When Autodetect Can Still Be Useful

Autodetect is a useful feature in some cases. For quick prototypes, small datasets, or ad-hoc analysis, automatic relationship detection can save time. However, once a model moves toward production or supports business-critical reporting, manual control is strongly recommended.

Thanks for reading!