You have a Tableau parameter named Measure Selector with values: Sales, Profit, and Quantity. You want to create a calculated field that dynamically returns the selected measure's value.
Which of the following calculated field formulas correctly implements this dynamic measure swap?
Remember that you need to aggregate the measures inside the calculated field to work correctly in Tableau.
Option D uses a CASE statement with aggregation functions SUM() for each measure, which is the correct way to dynamically swap measures based on a parameter in Tableau.
Option D uses valid IF-ELSEIF syntax but CASE is the preferred and more readable approach for multiple conditions in Tableau calculated fields.
Option D returns row-level values without aggregation, which will cause errors in aggregated views.
Option D uses SWITCH syntax which is not valid in Tableau calculated fields.
You have implemented a dynamic measure swap in Tableau using a parameter to switch between Sales, Profit, and Quantity. You want to create a dashboard that clearly shows the selected measure over time.
Which visualization type is best suited to display this dynamic measure swap effectively?
Think about how to best show changes over time for a single selected measure.
A line chart is ideal to show trends over time for one measure, which fits the dynamic measure swap scenario.
Pie charts and stacked bars show multiple measures at once, which conflicts with the idea of swapping a single measure dynamically.
Scatter plots compare two measures, not suitable for a single dynamic measure over time.
You want to implement a dynamic measure swap in Tableau that allows users to select from multiple measures stored in different fact tables (e.g., Sales fact, Inventory fact).
What is the best data modeling approach to support this dynamic measure swap efficiently?
Think about how to unify measures from different tables into one structure for easy swapping.
Option A creates a single combined fact table with a measure type and value, which simplifies dynamic measure swapping.
Option A complicates the model with multiple parameters and calculated fields.
Option A (blending) is less efficient and harder to maintain.
Option A duplicates data sources, which is inefficient and not scalable.
You created a calculated field for dynamic measure swap using this formula:
IF [Measure Selector] = 'Sales' THEN [Sales] ELSEIF [Measure Selector] = 'Profit' THEN [Profit] ELSE [Quantity] END
When you use this field in a view aggregated by month, the values are incorrect or missing.
What is the main reason for this issue?
Think about aggregation requirements when using calculated fields in aggregated views.
The calculated field returns raw row-level values without aggregation (SUM or AVG), so Tableau cannot aggregate them correctly in a monthly view.
Option A is unlikely if parameter values match.
Option A is incorrect because ELSEIF is valid syntax.
Option A would cause errors but not incorrect aggregation.
You have a large dataset and implemented a dynamic measure swap using a parameter and a calculated field with multiple SUM aggregations. Users report slow dashboard performance.
Which approach will most effectively improve performance while keeping the dynamic measure swap functionality?
Think about reducing the amount of data Tableau processes at runtime.
Pre-aggregating data reduces the volume Tableau processes, improving performance while keeping dynamic swapping.
Option B filters data but does not reduce aggregation complexity.
Option B loses the dynamic swapping benefit.
Option B often increases complexity and can hurt performance.