Statistical summary card in Tableau - Real Business Scenario
| Date | Region | Product Category | Sales Amount | Quantity Sold |
|---|---|---|---|---|
| 2024-01-05 | North | Electronics | 1200 | 3 |
| 2024-01-15 | South | Furniture | 850 | 2 |
| 2024-02-10 | East | Electronics | 600 | 1 |
| 2024-02-20 | West | Clothing | 400 | 5 |
| 2024-03-05 | North | Furniture | 1500 | 4 |
| 2024-03-15 | South | Clothing | 300 | 3 |
| 2024-03-25 | East | Electronics | 700 | 2 |
| 2024-03-30 | West | Furniture | 950 | 1 |
Use Tableau's data connection wizard to import the data.Drag the Date field to Filters, select Range of Dates, and set from 2024-01-01 to 2024-03-31.Create calculated field named 'Total Sales' with formula: SUM([Sales Amount])Create calculated field named 'Average Sales' with formula: AVG([Sales Amount])Create calculated field named 'Max Sale' with formula: MAX([Sales Amount])Create calculated field named 'Total Quantity' with formula: SUM([Quantity Sold])Use Text objects or KPI cards in Tableau dashboard, each showing one calculated field with clear labels.Adjust font size to at least 18pt, use dark text on light background, and align cards side by side.--------------------------------------------- | Total Sales | Average Sales | Max Sale | Total Quantity | | $6,000 | $750.00 | $1,500 | 21 | ---------------------------------------------
Add a trend line chart below the summary cards showing total sales by month for the last quarter.
Practice
What is the main purpose of a statistical summary card in Tableau dashboards?
Solution
Step 1: Understand the role of summary cards
Summary cards highlight important numbers like totals or averages for quick insight.Step 2: Compare options with this purpose
Only To show key numbers clearly and simply matches the purpose of showing key numbers simply and clearly.Final Answer:
To show key numbers clearly and simply -> Option DQuick Check:
Summary card = clear key numbers [OK]
- Confusing summary cards with detailed tables
- Thinking summary cards create data models
- Assuming summary cards are for maps
Which of the following is the correct way to create a SUM aggregation for a measure named Sales in Tableau?
Solution
Step 1: Recall Tableau aggregation syntax
Tableau uses square brackets for field names inside aggregation functions.Step 2: Check each option
OnlySUM([Sales])uses correct syntax with brackets and parentheses.Final Answer:
SUM([Sales]) -> Option AQuick Check:
SUM with brackets = SUM([Sales]) [OK]
- Omitting square brackets around field names
- Using curly braces instead of parentheses
- Using colon instead of parentheses
Given a dataset with Sales values: 100, 200, 300, what will the AVG([Sales]) aggregation show on a summary card?
Solution
Step 1: Calculate the average of Sales values
Sum is 100 + 200 + 300 = 600; count is 3.Step 2: Compute average
Average = 600 / 3 = 200.Final Answer:
200 -> Option BQuick Check:
AVG = sum/count = 200 [OK]
- Choosing sum instead of average
- Picking a single value instead of average
- Confusing average with maximum
Which of the following formulas will cause an error when used in a Tableau summary card?
IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low' END
Solution
Step 1: Understand Tableau IF statement syntax
Tableau IF statements must end withENDkeyword.Step 2: Check each option for missing END
IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low'is missingEND, causing syntax error.Final Answer:
IF SUM([Sales]) > 100 THEN 'High' ELSE 'Low' -> Option CQuick Check:
Missing END causes error [OK]
- Forgetting END keyword in IF statements
- Using wrong comparison operators
- Misplacing THEN or ELSE keywords
You want to create a summary card showing the COUNT of unique customers who made purchases over $500. Which Tableau calculation should you use?
Solution
Step 1: Identify requirement for unique count of customers
UseCOUNTDto count distinct customer IDs.Step 2: Filter customers with sales over $500
Use IF to include only customers where[Sales] > 500.Step 3: Combine into calculation
COUNTD(IF [Sales] > 500 THEN [Customer ID] END)counts unique customers meeting condition.Final Answer:
COUNTD(IF [Sales] > 500 THEN [Customer ID] END) -> Option AQuick Check:
Unique count with condition = COUNTD(IF...) [OK]
- Using COUNT instead of COUNTD for unique counts
- Using SUM or AVG instead of count functions
- Not filtering with IF condition properly
Ready to prove it?
Pass the test and this pattern moves unknown
