Treemap in Power BI - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ visualization

intermediate

Understanding Treemap Area Representation

You have a treemap visual showing sales by product category. The size of each rectangle represents total sales amount. If the sales for 'Electronics' is twice that of 'Clothing', how will their areas compare?

A Both rectangles will have the same area regardless of sales.

B The 'Electronics' rectangle will be twice as large in area as 'Clothing'.

C The 'Clothing' rectangle will be larger because it has more categories.

D The size depends on the number of products, not sales amount.

💡 Hint

Think about what the size of each block in a treemap represents.

In a treemap, the area of each rectangle is proportional to the value it represents. So if 'Electronics' sales are twice 'Clothing', its area will be twice as large.

❓ dax_lod_result

intermediate

DAX Measure for Treemap Size by Category

Given a sales table with columns Category and SalesAmount, which DAX measure correctly calculates total sales per category for a treemap?

A Total Sales = CALCULATE(SUM(Sales[SalesAmount]), ALL(Sales))

B Total Sales = SUMX(VALUES(Sales[Category]), Sales[SalesAmount])

C Total Sales = SUM(Sales[SalesAmount])

D Total Sales = COUNT(Sales[SalesAmount])

💡 Hint

Think about how to sum sales amounts grouped by category.

The measure SUM(Sales[SalesAmount]) sums sales amounts and when used in a treemap with category on axis, it calculates total sales per category.

❓ data_modeling

advanced

Modeling Data for Multi-Level Treemap

You want to create a treemap showing sales by Region and then by City within each region. Which data model setup is best?

A Have a single sales table with columns for Region, City, and SalesAmount.

B Create separate tables for Region and City with no relationships to sales.

C Create a disconnected table for Region and link City to sales.

D Use only a City table and ignore Region for simplicity.

💡 Hint

Think about how treemap groups data hierarchically.

A single sales table with Region and City columns allows the treemap to group sales by Region first, then City, showing hierarchical areas correctly.

🔧 Formula Fix

advanced

Troubleshooting Treemap Showing Incorrect Sizes

Your treemap visual shows all categories with equal size, even though sales differ. What is the most likely cause?

A The category field is not added to the treemap.

B The treemap visual does not support size differences.

C The data source has no sales data at all.

D The measure used is a count of categories instead of sum of sales.

💡 Hint

Check what the measure is calculating.

If the measure counts categories instead of summing sales, each category will have the same count (usually 1), making all areas equal.

🧠 Conceptual

expert

Best Practice for Color Usage in Treemaps

Which color strategy improves accessibility and clarity in a treemap showing product categories with sales values?

A Use a single color hue with varying brightness to represent sales values.

B Use random bright colors for each category without a legend.

C Use red for high sales and green for low sales regardless of categories.

D Use grayscale colors only to avoid distraction.

💡 Hint

Think about how color differences help users understand data clearly.

Using one color hue with brightness variation helps users easily compare values while maintaining color harmony and accessibility.

Practice

1. What is the main purpose of a Treemap visualization in Power BI?

easy

A. To list data in rows and columns

B. To display data as a line over time

C. To show parts of a whole using size and color

D. To create a map with geographic locations

Solution

1. Step 1: Understand Treemap visualization

   A Treemap shows data as nested rectangles where size and color represent values.

2. Step 2: Compare options to definition

   Only To show parts of a whole using size and color describes showing parts of a whole using size and color, which matches Treemap.

3. Final Answer:

   To show parts of a whole using size and color -> Option C

4. Quick Check:

   Treemap = parts of whole with size and color [OK]

Hint: Treemap = parts of whole shown by size and color [OK]

Common Mistakes:

• Confusing Treemap with line chart
• Thinking Treemap is a table
• Mixing Treemap with map visual

2. Which fields should you add to a Treemap visual in Power BI to show category sizes correctly?

easy

A. Add 'Group' to Tooltip and 'Values' to Axis

B. Add 'Group' to Values and 'Values' to Legend

C. Add 'Values' to Group and 'Group' to Values

D. Add 'Group' to Group and 'Values' to Values

Solution

1. Step 1: Recall Treemap field roles

   Treemap uses 'Group' for categories and 'Values' for size of rectangles.

2. Step 2: Match fields to correct roles

   Add 'Group' to Group and 'Values' to Values correctly assigns 'Group' to Group and 'Values' to Values, which is required.

3. Final Answer:

   Add 'Group' to Group and 'Values' to Values -> Option D

4. Quick Check:

   Group = Group, Values = Values [OK]

Hint: Group goes to Group, Values goes to Values in Treemap [OK]

Common Mistakes:

• Swapping Group and Values fields
• Putting Values in Legend or Axis incorrectly
• Using Tooltip instead of Group or Values

3. Given a dataset with categories and sales amounts, what will a Treemap show if one category has sales 500 and another 1000?

medium

A. The category with 1000 sales will have a rectangle twice as large as the 500 sales category

B. Both categories will have rectangles of the same size

C. The category with 500 sales will have a rectangle twice as large as the 1000 sales category

D. The Treemap will only show color differences, not size

Solution

1. Step 1: Understand Treemap size representation

   Treemap rectangle size is proportional to the value it represents.

2. Step 2: Compare sales values

   1000 is twice 500, so the rectangle for 1000 sales will be twice as large as for 500 sales.

3. Final Answer:

   The category with 1000 sales will have a rectangle twice as large as the 500 sales category -> Option A

4. Quick Check:

   Size ∝ Value, so 1000 sales rectangle is twice 500 sales [OK]

Hint: Rectangle size matches value proportionally in Treemap [OK]

Common Mistakes:

• Thinking smaller value has bigger rectangle
• Assuming rectangles are same size
• Believing Treemap uses only color, not size

4. You created a Treemap but all rectangles appear the same size despite different values. What is the most likely cause?

medium

A. You added the 'Group' field to Values instead of 'Values'

B. You used a stacked bar chart instead of Treemap

C. You forgot to add any fields to the visual

D. You added 'Values' to Group and 'Group' to Values

Solution

1. Step 1: Analyze field placement impact

   Adding 'Group' to Values means Power BI treats categories as numeric values, causing equal sizes.

2. Step 2: Identify correct field usage

   Values field must be numeric data for size; Group is categorical and should not be in Values.

3. Final Answer:

   You added the 'Group' field to Values instead of 'Values' -> Option A

4. Quick Check:

   Wrong field in Values causes equal rectangle sizes [OK]

Hint: Ensure numeric field is in Values, not Group [OK]

Common Mistakes:

• Swapping Group and Values fields
• Using wrong visual type
• Leaving fields empty

5. You want to create a Treemap showing sales by product category and highlight categories with sales above 1000 in a different color. How can you achieve this in Power BI?

hard

A. Add 'Sales' to Group and 'Group' to Values, then filter categories with sales > 1000

B. Add 'Group' to Group, 'Sales' to Values, and create a measure with conditional color formatting based on sales > 1000

C. Use a stacked bar chart instead and apply color rules

D. Add 'Group' to Tooltip and 'Sales' to Legend without conditional formatting

Solution

1. Step 1: Set up Treemap fields correctly

   Add 'Group' to Group for categories and 'Sales' to Values for size representation.

2. Step 2: Apply conditional color formatting

   Create a measure that returns different colors based on sales > 1000, then use it in color formatting.

3. Final Answer:

   Add 'Group' to Group, 'Sales' to Values, and create a measure with conditional color formatting based on sales > 1000 -> Option B

4. Quick Check:

   Correct fields + conditional color measure = desired Treemap [OK]

Hint: Use conditional color measure with correct fields in Treemap [OK]

Common Mistakes:

• Swapping Group and Values fields
• Not using conditional formatting for color
• Choosing wrong visual type