Comprehensive and Detailed Explanation From Exact Extract:
Tableau's Performance Optimizer flags nested calculations because:
* They produce more complex queries inside the extract engine.
* They require additional computation during query execution.
* They slow down extract-based workbooks because all internal logic must run inside Hyper, not the database.
Tableau documentation provides two recommended solutions:
Solution 1: Move calculations upstream (Option A)
When calculations are performed in the database or data-prep layer, the extract does not need to compute them at runtime.
Benefits include:
* Hyper extracts become simpler
* Query execution becomes faster
* No nested expressions inside Tableau
This matches Option A.
Solution 2: Use "Compute Calculations Now" when publishing (Option C)
"Compute Calculations Now" allows Tableau to:
* Materialize eligible calculations inside the extract
* Reduce the runtime load
* Remove nested calculation layers during query execution
This option is specifically documented as a solution to Performance Optimizer warnings related to calculated fields in extracts.
Therefore, Option C is also correct.
Why the other answers are incorrect:
B). Add "Apply" to filters
Improves dashboard interactivity, not extract query complexity.
D). Hide nested calculations
Hiding fields has no effect on extract computation - they remain part of the data model.
* Extract optimization recommendations
* "Compute Calculations Now" extract materialization documentation
* Performance Optimizer guidance on nested calculations