Tooltip customization in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ visualization

intermediate

Customize Tooltip to Show Sales and Profit

You have a sales dashboard in Tableau. You want the tooltip to show both Sales and Profit values when hovering over a data point.

Which tooltip customization will correctly display both values?

A <p>Sales: <code><SUM([Sales])></code><br>Profit: <code><SUM([Profit])></code></p>

B <p>Sales: <code><SUM([Sales])></code></p>

C <p>Sales: <code><b><SUM([Sales])></b></code><br>Profit: <code><b><SUM([Profit])></b></code></p>

D <p>Sales: <code><SUM([Sales])></code><br>Profit: <code><SUM([Profit])></code><br>Discount: <code><SUM([Discount])></code></p>

💡 Hint

Remember to use the correct syntax for inserting field values inside tooltips.

Option A correctly uses the syntax to insert aggregated values in the tooltip. Option A uses invalid tags. Option A adds an extra field not requested. Option A only shows Sales.

🧠 Conceptual

intermediate

Purpose of Tooltip Customization in Tableau

Why is customizing tooltips important in Tableau dashboards?

A To filter data permanently based on user clicks.

B To change the color of the dashboard background.

C To add more detailed information about data points without cluttering the main view.

D To export data directly from the tooltip.

💡 Hint

Think about what tooltips do when you hover over data.

Tooltips provide extra details on demand, helping users understand data points better without adding clutter. Options A, B, and D describe unrelated features.

❓ dax_lod_result

advanced

Calculate Average Sales per Category in Tooltip

You want to show the average sales per product category in a tooltip using a Level of Detail (LOD) expression in Tableau.

Which LOD expression correctly calculates this?

A AVG({ FIXED [Category] : SUM([Sales]) })

B { INCLUDE [Category] : SUM([Sales]) }

C { EXCLUDE [Category] : AVG([Sales]) }

D { FIXED [Category] : AVG([Sales]) }

💡 Hint

LOD expressions use FIXED, INCLUDE, or EXCLUDE to control aggregation levels.

Option D fixes the calculation at the category level and averages sales correctly. Option D sums sales and includes category, which is not average. Option D excludes category, changing the level incorrectly. Option D averages category totals instead of sales per category.

🔧 Formula Fix

advanced

Fix Tooltip Showing Incorrect Profit Values

Your tooltip shows profit values that are too high. You suspect the aggregation is wrong.

Which of these tooltip expressions is causing the error?

A <p>Profit: <code><ATTR([Profit])></code></p>

B <p>Profit: <code><SUM([Profit])></code></p>

C <p>Profit: <code><AVG([Profit])></code></p>

D <p>Profit: <code><MIN([Profit])></code></p>

💡 Hint

ATTR returns a single value if all rows have the same value, else it shows an asterisk.

Using ATTR([Profit]) in a tooltip aggregates incorrectly when multiple rows exist, causing misleading values. SUM or AVG are appropriate aggregations for profit. MIN is valid but shows minimum, not total.

🎯 Scenario

expert

Design Tooltip to Show Dynamic Text Based on Sales Threshold

You want a tooltip that shows the text "High Sales" if sales are above 100,000 and "Low Sales" otherwise.

Which calculated field expression will produce this dynamic tooltip text?

A IF [Sales] > 100000 THEN 'High Sales' ELSE 'Low Sales' END

B IF SUM([Sales]) > 100000 THEN 'High Sales' ELSE 'Low Sales' END

C CASE WHEN SUM([Sales]) > 100000 THEN 'High Sales' ELSE 'Low Sales' END

D IF AVG([Sales]) > 100000 THEN 'High Sales' ELSE 'Low Sales' END

💡 Hint

Remember to aggregate sales before comparing to a threshold in Tableau calculated fields.

Option B correctly aggregates sales with SUM before comparison. Option B compares row-level [Sales], which may be invalid in tooltip context. Option B uses CASE WHEN syntax, which Tableau does not support. Option B uses AVG which changes logic.