Why LOD expressions control aggregation scope in Tableau - Dashboard Impact

Dashboard Mode - Why LOD expressions control aggregation scope

Business Question

How can we use Level of Detail (LOD) expressions in Tableau to control the scope of data aggregation and get precise insights?

Sample Data

Region	Category	Sales	Order ID
East	Furniture	300	1001
East	Office Supplies	200	1002
West	Furniture	400	1003
West	Technology	500	1004
East	Technology	600	1005
West	Office Supplies	150	1006
East	Furniture	350	1007

Dashboard Components

• KPI Card: Total Sales
  Formula: SUM([Sales])
  Result: 2,500
  Shows total sales across all regions and categories.
• KPI Card: Sales per Region (Fixed LOD)
  Formula: {FIXED [Region]: SUM([Sales])}
  Example for East: 1,450
  Shows total sales fixed at Region level, ignoring other filters.
• Bar Chart: Sales by Category
  Aggregates sales by category using SUM([Sales])
  Bars show Furniture: 1,050; Office Supplies: 350; Technology: 1,100.
• Table: Average Sales per Order (Include LOD)
  Formula: {INCLUDE [Order ID]: AVG([Sales])}
  Calculates average sales per order considering each order uniquely.

Dashboard Layout

+----------------------+-------------------------+
| Total Sales (KPI)    | Sales per Region (KPI)  |
+----------------------+-------------------------+
|                          Bar Chart: Sales by Category          |
+--------------------------------------------------------------+
|           Table: Average Sales per Order (Include LOD)       |
+--------------------------------------------------------------+

Interactivity

Filters on Region or Category update the Bar Chart and Table dynamically. The {FIXED [Region]: SUM([Sales])} KPI ignores category filters and always shows total sales per region. The Total Sales KPI updates with all filters applied.

Self Check

If you add a filter for Category = Furniture, which components update and how?

• Total Sales KPI updates to sum sales only for Furniture (1,050).
• Sales per Region KPI remains fixed per region ignoring category filter (East: 650; West: 400).
• Bar Chart updates to show only Furniture sales by category (only Furniture category bars remain).
• Average Sales per Order Table updates to average sales for Furniture orders only.

Key Result

Dashboard showing how LOD expressions control aggregation scope with KPIs, bar chart, and table using sales data by region and category.

Practice

1. What is the main purpose of Level of Detail (LOD) expressions in Tableau?

easy

A. To export data to Excel automatically

B. To change the color of charts dynamically

C. To filter data based on user input

D. To control how data is grouped before aggregation

Solution

1. Step 1: Understand LOD expression role

   LOD expressions let you fix or change the grouping level before aggregation happens.

2. Step 2: Compare with other options

   Changing colors, filtering, or exporting are unrelated to aggregation scope control.

3. Final Answer:

   To control how data is grouped before aggregation -> Option D

4. Quick Check:

   LOD controls grouping before aggregation = A [OK]

Hint: LOD fixes grouping level before aggregation [OK]

Common Mistakes:

• Confusing LOD with filtering
• Thinking LOD changes chart colors
• Assuming LOD exports data

2. Which of the following is the correct syntax for a FIXED LOD expression in Tableau?

easy

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

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

C. { EXCLUDE [Region] : AVG([Sales]) }

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

Solution

1. Step 1: Identify correct FIXED syntax

   FIXED LOD syntax is { FIXED [Dimension] : Aggregation }, so { FIXED [Region] : SUM([Sales]) } matches.

2. Step 2: Check other options

   Options A and B use different LOD types, and D has incorrect order.

3. Final Answer:

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

4. Quick Check:

   FIXED syntax = { FIXED [Dimension] : Aggregation } [OK]

Hint: FIXED syntax: { FIXED [Dimension] : Aggregation } [OK]

Common Mistakes:

• Swapping dimension and aggregation order
• Using INCLUDE or EXCLUDE instead of FIXED
• Missing curly braces

3. Given the data view grouped by [Category], what will { FIXED [Category] : SUM([Sales]) } return compared to SUM([Sales])?

medium

A. FIXED returns total sales ignoring Category grouping

B. SUM returns total sales ignoring Category grouping

C. Both return the same total sales per category

D. FIXED returns average sales per category

Solution

1. Step 1: Understand FIXED with grouping

   FIXED on [Category] fixes aggregation at category level, matching the view's grouping.

2. Step 2: Compare with SUM aggregation

   SUM([Sales]) aggregated by Category in the view also sums sales per category.

3. Final Answer:

   Both return the same total sales per category -> Option C

4. Quick Check:

   FIXED on grouping dimension = same as SUM by that group [OK]

Hint: FIXED on grouped dimension equals normal aggregation [OK]

Common Mistakes:

• Thinking FIXED ignores grouping always
• Confusing FIXED with INCLUDE or EXCLUDE
• Assuming FIXED changes aggregation type

4. Identify the error in this LOD expression: { FIXED : SUM([Sales]) }

medium

A. Missing dimension after FIXED keyword

B. SUM aggregation is not allowed in LOD

C. Curly braces are not needed

D. FIXED cannot be used without INCLUDE or EXCLUDE

Solution

1. Step 1: Check FIXED syntax requirements

   FIXED requires at least one dimension to fix aggregation scope, missing here.

2. Step 2: Validate other parts

   SUM is valid aggregation, curly braces are required, and FIXED can be used alone.

3. Final Answer:

   Missing dimension after FIXED keyword -> Option A

4. Quick Check:

   FIXED needs dimension(s) specified [OK]

Hint: FIXED must specify dimension(s) after keyword [OK]

Common Mistakes:

• Leaving out dimension after FIXED
• Removing curly braces
• Confusing FIXED with INCLUDE/EXCLUDE requirement

5. You want to calculate the total sales per customer ignoring the current view's grouping by product. Which LOD expression should you use?

hard

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

B. { FIXED [Customer] : SUM([Sales]) }

C. { EXCLUDE [Customer] : SUM([Sales]) }

D. { FIXED [Product] : SUM([Sales]) }

Solution

1. Step 1: Understand requirement

   You want total sales per customer ignoring product grouping in the view.

2. Step 2: Choose correct LOD type

   FIXED on [Customer] fixes aggregation at customer level, ignoring other groupings like product.

3. Step 3: Evaluate options

   INCLUDE adds dimensions, EXCLUDE removes dimensions incorrectly here, FIXED on product fixes wrong dimension.

4. Final Answer:

   { FIXED [Customer] : SUM([Sales]) } -> Option B

5. Quick Check:

   FIXED fixes aggregation ignoring view grouping [OK]

Hint: Use FIXED on dimension to ignore view grouping [OK]

Common Mistakes:

• Using INCLUDE or EXCLUDE instead of FIXED
• Fixing wrong dimension
• Confusing FIXED with filtering