LOD vs table calculations in Tableau - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference in Calculation Scope

Which statement best describes the difference between Level of Detail (LOD) expressions and table calculations in Tableau?

A Table calculations are computed before data aggregation, whereas LOD expressions are computed after aggregation.

B LOD expressions compute values at the data source level, independent of the view, while table calculations compute values based on the data visible in the view.

C LOD expressions only work on aggregated data, while table calculations work on row-level data.

D Table calculations require data blending, but LOD expressions do not.

💡 Hint

Think about when and where each calculation happens in the data processing flow.

LOD expressions fix the level of detail regardless of the view's dimensions, computing values at the data source level. Table calculations operate on the data after it is loaded into the view, using the visible data.

❓ dax_lod_result

intermediate

LOD Expression Result

Given a dataset with sales data by Region and Product, what is the result of this LOD expression?

{ FIXED [Region] : SUM([Sales]) }

If the view shows data by Product only, what does this expression return?

A The total sales summed by each Region, ignoring Product in the view.

B The total sales summed by each Product, ignoring Region.

C The total sales summed for the entire dataset, ignoring Region and Product.

D An error because Region is not in the view.

💡 Hint

Remember that FIXED LOD expressions calculate independently of the view's dimensions.

The FIXED LOD expression calculates the sum of sales for each Region regardless of the dimensions in the view. Even if Product is in the view, the calculation is fixed at Region level.

❓ visualization

advanced

Choosing the Right Calculation Type

You want to show the percentage of total sales for each Product within each Region. Which approach is best?

A Use a INCLUDE LOD expression to add Product level detail to Region totals.

B Use a table calculation to compute percent of total sales across the entire dataset ignoring Region.

C Use a FIXED LOD expression to calculate total sales by Product across all Regions.

D Use a table calculation to compute the percent of total sales partitioned by Region.

💡 Hint

Think about how to calculate percentages within each Region shown in the view.

A table calculation partitioned by Region computes the percent of total sales for each Product within that Region, which matches the requirement.

🔧 Formula Fix

advanced

Fixing Unexpected Results with LOD

You created this LOD expression:

{ INCLUDE [Product] : SUM([Sales]) }

But the results are higher than expected when the view includes Region and Product. What is the likely cause?

A The INCLUDE LOD adds Product detail, causing sales to be summed multiple times if Region is also in the view.

B The data source has duplicate rows causing inflated sums.

C The FIXED LOD should be used instead of INCLUDE to avoid duplication.

D The LOD expression syntax is incorrect and causes a calculation error.

💡 Hint

Consider how INCLUDE LOD expressions aggregate data relative to the view's dimensions.

INCLUDE LOD expressions add detail to the aggregation. If the view already includes Region and Product, the aggregation may double count sales, leading to higher results.

🎯 Scenario

expert

Combining LOD and Table Calculations

You want to show the rank of each Product's sales within each Region, but the rank should be based on total sales fixed at the Region level, ignoring Product filters in the view. Which approach achieves this?

A Use a FIXED LOD expression to rank Products within each Region directly.

B Use a table calculation to rank Products by sales, then apply a FIXED LOD to filter by Region.

C Create a FIXED LOD expression to calculate total sales by Region, then use a table calculation to rank Products within each Region based on that fixed total.

D Use a table calculation partitioned by Product to rank sales ignoring Region.

💡 Hint

Think about how to fix totals at Region level and then rank Products within that fixed context.

First, FIXED LOD calculates total sales by Region ignoring Product filters. Then, a table calculation ranks Products within each Region based on those fixed totals, achieving the desired result.

Practice

1. What is the main difference between LOD expressions and table calculations in Tableau?

easy

A. LOD expressions fix calculations at a specific data level, ignoring some filters, while table calculations work on the data shown in the current view.

B. LOD expressions only work on aggregated data, while table calculations only work on raw data.

C. LOD expressions are faster than table calculations in all cases.

D. Table calculations ignore filters, but LOD expressions depend on the table layout.

Solution

1. Step 1: Understand LOD expressions

   LOD expressions fix the calculation at a certain level of detail, ignoring some filters applied to the view.

2. Step 2: Understand table calculations

   Table calculations work on the data currently displayed in the view and depend on how the table is laid out.

3. Final Answer:

   LOD expressions fix calculations at a specific data level, ignoring some filters, while table calculations work on the data shown in the current view. -> Option A

4. Quick Check:

   LOD fixes level, table calculations depend on view [OK]

Hint: LOD fixes level, table calculations depend on view layout [OK]

Common Mistakes:

• Thinking table calculations ignore filters
• Believing LOD always works on raw data
• Assuming LOD is always faster

2. Which of the following is the correct syntax for a fixed LOD expression in Tableau to calculate total sales per region?

easy

A. { EXCLUDE [Region] : SUM([Sales]) }

B. { INCLUDE [Region] : SUM([Sales]) }

C. { FIXED [Region] : SUM([Sales]) }

D. SUM([Sales]) FIXED BY [Region]

Solution

1. Step 1: Recall fixed LOD syntax

   The fixed LOD syntax is { FIXED [Dimension] : Aggregation }.

2. Step 2: Match syntax to question

   { FIXED [Region] : SUM([Sales]) } matches the correct syntax for total sales per region.

3. Final Answer:

   { FIXED [Region] : SUM([Sales]) } -> Option C

4. Quick Check:

   Fixed LOD uses FIXED keyword and curly braces [OK]

Hint: Fixed LOD always starts with { FIXED ... } [OK]

Common Mistakes:

• Using INCLUDE or EXCLUDE instead of FIXED
• Missing curly braces
• Incorrect keyword order

3. Given a view showing sales by category and sub-category, what will the following LOD expression return?
{ FIXED [Category] : SUM([Sales]) }

medium

A. Total sales for each sub-category ignoring category

B. Total sales for each category repeated for all sub-categories within it

C. Total sales for the entire dataset ignoring category and sub-category

D. Running total of sales by sub-category

Solution

1. Step 1: Understand FIXED by Category

   The expression fixes sales at the category level, ignoring sub-category detail.

2. Step 2: Effect on sub-category rows

   Each sub-category row will show the total sales of its parent category, repeated.

3. Final Answer:

   Total sales for each category repeated for all sub-categories within it -> Option B

4. Quick Check:

   Fixed LOD repeats category total per sub-category [OK]

Hint: Fixed LOD repeats fixed level value for lower detail rows [OK]

Common Mistakes:

• Thinking it sums only sub-category sales
• Confusing FIXED with INCLUDE or EXCLUDE
• Assuming running total behavior

4. You created a table calculation for running total of sales but it shows incorrect results. Which of the following is the most likely cause?

medium

A. The filter is applied before the LOD calculation.

B. The LOD expression used is FIXED instead of INCLUDE.

C. The data source is missing a join condition.

D. The table calculation is not set to compute using the correct dimension.

Solution

1. Step 1: Understand table calculation behavior

   Table calculations depend on the table layout and the dimension used for computation.

2. Step 2: Identify common error

   If the running total is wrong, often the compute using dimension is set incorrectly.

3. Final Answer:

   The table calculation is not set to compute using the correct dimension. -> Option D

4. Quick Check:

   Table calcs need correct compute using dimension [OK]

Hint: Check 'compute using' dimension for table calculations [OK]

Common Mistakes:

• Confusing LOD and table calculation errors
• Blaming data joins for table calc issues
• Ignoring table layout impact

5. You want to show the percent of total sales by region in a view that filters by year. Which approach is best to ensure the percent always reflects all years, ignoring the year filter?

hard

A. Use a FIXED LOD expression to calculate total sales by region ignoring the year filter, then divide sales by this fixed total.

B. Use a table calculation for percent of total sales by region, which automatically ignores filters.

C. Apply the year filter after creating a table calculation for percent of total sales.

D. Use an INCLUDE LOD expression including year to calculate sales.

Solution

1. Step 1: Understand filter impact on calculations

   Table calculations and INCLUDE LOD respect filters, so year filter affects them.

2. Step 2: Use FIXED LOD to ignore year filter

   FIXED LOD can ignore filters like year, fixing total sales by region across all years.

3. Step 3: Calculate percent of total

   Divide sales by the fixed total sales to get percent ignoring year filter.

4. Final Answer:

   Use a FIXED LOD expression to calculate total sales by region ignoring the year filter, then divide sales by this fixed total. -> Option A

5. Quick Check:

   FIXED LOD ignores filters, perfect for fixed percent totals [OK]

Hint: Use FIXED LOD to ignore filters for fixed percent totals [OK]

Common Mistakes:

• Using table calculations that respect filters
• Using INCLUDE LOD which respects filters
• Applying filters after calculations incorrectly