Parameter in calculated fields in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ dax_lod_result

intermediate

Using Parameter in a Calculated Field to Filter Sales

You have a parameter named SelectedRegion with values: 'East', 'West', 'Central'. You create a calculated field:

IF [Region] = [SelectedRegion] THEN [Sales] ELSE 0 END

What will be the sum of this calculated field if the parameter is set to 'West' and the data contains sales for all regions?

A Sum of sales for all regions except West

B Sum of sales for all regions

C Zero, because parameters cannot be used in calculated fields

D Sum of sales only for the West region

💡 Hint

Think about how the parameter value filters the calculation.

The calculated field returns sales only when the region matches the parameter value. So, summing it gives total sales for the selected region.

❓ visualization

intermediate

Visualizing Sales by Dynamic Category Using Parameter

You create a parameter CategorySelector with values 'Category A', 'Category B', and 'Category C'. You use this parameter in a calculated field to show sales for the selected category. Which visualization best helps users understand sales changes when switching the parameter?

A A line chart showing sales over time with a filter for the selected category parameter

B A bar chart with sales on Y-axis and categories on X-axis, filtered by the parameter

C A pie chart showing sales distribution for all categories ignoring the parameter

D A scatter plot of sales vs. profit without using the parameter

💡 Hint

Consider how the parameter changes the category dynamically over time.

A line chart over time filtered by the parameter shows how sales for the selected category change dynamically.

🧠 Conceptual

advanced

Understanding Parameter Scope in Calculated Fields

Which statement about parameters used in Tableau calculated fields is correct?

A Parameters automatically update based on data changes without user input

B Parameters are static values that do not change unless the user interacts with them

C Parameters can dynamically filter data at the data source level before loading

D Parameters can be used to create dynamic sets that update automatically

💡 Hint

Think about how parameters behave compared to filters.

Parameters hold static values until the user changes them. They do not update automatically or filter data at the source.

❓ data_modeling

advanced

Using Parameter to Switch Measures in a Single View

You want to create a dashboard where users can select a measure (Sales, Profit, or Quantity) via a parameter and see the selected measure in a single chart. Which calculated field formula correctly uses the parameter MeasureSelector to switch measures?

A IF [MeasureSelector] = 'Sales' THEN SUM([Sales]) ELSEIF [MeasureSelector] = 'Profit' THEN SUM([Profit]) ELSE SUM([Quantity]) END

B CASE [MeasureSelector] WHEN 'Sales' THEN SUM([Sales]) WHEN 'Profit' THEN SUM([Profit]) ELSE SUM([Quantity]) END

C IF [MeasureSelector] = 'Sales' THEN [Sales] ELSEIF [MeasureSelector] = 'Profit' THEN [Profit] ELSE [Quantity] END

D SWITCH([MeasureSelector], 'Sales', SUM([Sales]), 'Profit', SUM([Profit]), SUM([Quantity]))

💡 Hint

Remember that aggregations like SUM should be applied to the calculated field in the view, not inside it.

Option C returns the raw measure without aggregation in the calculated field, which is correct; SUM is applied in the view. Options A and B mix aggregate and non-aggregate functions, causing errors. D uses invalid SWITCH syntax.

🔧 Formula Fix

expert

Debugging Parameter Usage in a Complex Calculated Field

Given the parameter DiscountRate (values 0, 0.05, 0.1) and the calculated field:

IF [DiscountRate] > 0 THEN [Sales] * (1 - [DiscountRate]) ELSE [Sales] END

Users report that the discount is not applied even when selecting 0.05 or 0.1. What is the most likely cause?

A The parameter is a string type, so the comparison [DiscountRate] > 0 always fails

B The parameter values are not connected to the calculated field properly

C The calculated field syntax is invalid and causes errors

D The ELSE clause overrides the discount calculation

💡 Hint

Check the data type of the parameter and how it is compared.

If the parameter is a string, comparing it to number 0 fails, so the IF condition is never true, and discount is never applied.