Card and multi-row card in Power BI - Real Business Scenario

Scenario Mode

👤 Your Role: You are a sales analyst at a retail company.

📋 Request: Your manager wants a quick summary dashboard showing total sales, total units sold, and average sales price per unit for the last quarter.

📊 Data: You have sales transaction data including Date, Product, Units Sold, and Sales Amount.

🎯 Deliverable: Create a Power BI report page with Card visuals for total sales and total units sold, and a Multi-row Card visual for average sales price per unit by product.

Sample Data

Date	Product	Units Sold	Sales Amount
2024-01-15	Widget A	10	200
2024-01-20	Widget B	5	150
2024-02-05	Widget A	8	160
2024-02-18	Widget C	12	360
2024-03-10	Widget B	7	210
2024-03-22	Widget C	6	180
2024-04-01	Widget A	9	180
2024-04-15	Widget B	4	120

1

Step 1: Filter data to include only sales from the last quarter (January to March 2024).

Apply a date filter on the Date column: Date >= DATE(2024,1,1) and Date <= DATE(2024,3,31).

Expected Result

Filtered data includes 6 rows from January to March 2024.

2

Step 2: Create a measure for Total Sales.

Total Sales = SUM('Sales'[Sales Amount])

Expected Result

Total Sales measure sums to 1260 for filtered data.

3

Step 3: Create a measure for Total Units Sold.

Total Units Sold = SUM('Sales'[Units Sold])

Expected Result

Total Units Sold measure sums to 48 for filtered data.

4

Step 4: Create a measure for Average Sales Price per Unit.

Average Price per Unit = DIVIDE([Total Sales], [Total Units Sold])

Expected Result

Average Price per Unit calculates to 26.25.

5

Step 5: Create a Card visual and add the Total Sales measure to it.

Visual type: Card; Field: Total Sales

Expected Result

Card visual displays 1260.

6

Step 6: Create a Card visual and add the Total Units Sold measure to it.

Visual type: Card; Field: Total Units Sold

Expected Result

Card visual displays 48.

7

Step 7: Create a measure for Average Sales Price per Unit by Product.

Average Price per Unit by Product = DIVIDE(SUM('Sales'[Sales Amount]), SUM('Sales'[Units Sold]))

Expected Result

Calculates average price per unit for each product.

8

Step 8: Create a Multi-row Card visual and add Product and Average Price per Unit by Product measure.

Visual type: Multi-row Card; Fields: Product, Average Price per Unit by Product

Expected Result

Multi-row Card shows each product with its average price per unit: Widget A=20, Widget B=30, Widget C=30.

Final Result

-----------------------------
| Total Sales       |  1260  |
-----------------------------
| Total Units Sold  |   48   |
-----------------------------
| Average Price per Unit by Product |
| Widget A         |  20    |
| Widget B         |  30    |
| Widget C         |  30    |
-----------------------------

✓Total sales for the last quarter were $1,260.

✓A total of 48 units were sold in the last quarter.

✓Widget A has the lowest average price per unit at $20.

✓Widgets B and C have a higher average price per unit at $30.

Bonus Challenge

Add a slicer to the report to allow filtering the data by Product, updating all cards dynamically.

Show Hint

Use a slicer visual with the Product field and ensure all visuals interact with the slicer.

Practice

1. What is the main purpose of a Card visual in Power BI?

easy

A. To display a single important number clearly

B. To show multiple rows of data with labels

C. To create interactive filters for reports

D. To display detailed tables with many columns

Solution

1. Step 1: Understand Card visual function

   A Card visual is designed to show one key number or metric clearly on a report.

2. Step 2: Compare with other visuals

   Unlike Multi-row Card or tables, Card focuses on a single value without labels or rows.

3. Final Answer:

   To display a single important number clearly -> Option A

4. Quick Check:

   Card = single number [OK]

Hint: Card shows one number only, not multiple rows [OK]

Common Mistakes:

• Confusing Card with Multi-row Card
• Thinking Card shows multiple values
• Assuming Card is for filtering

2. Which of the following is the correct way to add a measure to a Card visual in Power BI?

easy

A. Drag the measure field into the Tooltip area of the Card visual

B. Drag the measure field into the Axis area of the Card visual

C. Drag the measure field into the Legend area of the Card visual

D. Drag the measure field into the Values area of the Card visual

Solution

1. Step 1: Identify Card visual field well

   The Card visual uses the Values area to display the number from a measure or column.

2. Step 2: Understand other areas

   Axis and Legend are for charts, not Card. Tooltip shows info on hover but not main display.

3. Final Answer:

   Drag the measure field into the Values area of the Card visual -> Option D

4. Quick Check:

   Card uses Values area for measure [OK]

Hint: Card visual only needs measure in Values area [OK]

Common Mistakes:

• Putting measure in Axis or Legend by mistake
• Confusing Tooltip with main display
• Trying to add multiple fields to Card

3. Given a Multi-row Card visual showing these fields: Sales Amount, Order Count, and Customer Count, what will the visual display?

medium

A. One single number combining all three fields

B. Three separate numbers each with their field label

C. A table with rows and columns for each field

D. A chart plotting Sales Amount over time

Solution

1. Step 1: Understand Multi-row Card behavior

   Multi-row Card shows multiple measures or columns as separate numbers with labels stacked vertically.

2. Step 2: Compare with other visuals

   It does not combine numbers into one or create tables or charts.

3. Final Answer:

   Three separate numbers each with their field label -> Option B

4. Quick Check:

   Multi-row Card = multiple labeled numbers [OK]

Hint: Multi-row Card shows each field with label separately [OK]

Common Mistakes:

• Thinking Multi-row Card sums fields
• Confusing Multi-row Card with table or chart
• Expecting combined or plotted data

4. You added a measure to a Multi-row Card but it shows blank instead of the expected number. What is the most likely cause?

medium

A. The measure has a filter that returns no data

B. The Multi-row Card does not support measures

C. You added the measure to the Axis area instead of Values

D. The data source is not connected

Solution

1. Step 1: Check measure calculation

   If a measure returns blank, often it is because filters applied cause no data to match.

2. Step 2: Verify Multi-row Card support

   Multi-row Card supports measures in Values area; Axis area does not exist for it.

3. Step 3: Confirm data connection

   If data source was disconnected, all visuals would fail, not just one measure.

4. Final Answer:

   The measure has a filter that returns no data -> Option A

5. Quick Check:

   Blank measure = no data due to filter [OK]

Hint: Blank measure usually means no data after filters [OK]

Common Mistakes:

• Thinking Multi-row Card can't show measures
• Trying to add measure to wrong field well
• Ignoring data connection issues

5. You want to create a dashboard showing total sales, total customers, and average order value clearly. Which visual setup is best?

hard

A. Use three separate Card visuals, one for each metric

B. Use a table visual listing all sales transactions

C. Use one Multi-row Card visual with all three measures

D. Use a line chart plotting sales over time

Solution

1. Step 1: Identify the need for multiple metrics

   You want to show three key numbers clearly with labels, so multiple values in one place is ideal.

2. Step 2: Compare visual options

   Three Cards would work but take more space; Multi-row Card shows all three metrics stacked with labels compactly.

3. Step 3: Exclude other visuals

   Table shows raw data, line chart shows trends, not summary numbers.

4. Final Answer:

   Use one Multi-row Card visual with all three measures -> Option C

5. Quick Check:

   Multi-row Card = multiple labeled metrics [OK]

Hint: Multi-row Card fits multiple metrics with labels compactly [OK]

Common Mistakes:

• Using multiple Cards wasting space
• Choosing tables or charts instead of summary visuals
• Not labeling metrics clearly