TDS-C01 Understanding Tableau Concepts

Understanding Tableau Concepts Detailed Explanation

This section explains fundamental Tableau concepts that every beginner needs to master, including Dimensions and Measures, Discrete vs. Continuous fields, and Aggregations. These concepts form the backbone of how Tableau handles and visualizes data.

1. Dimensions and Measures

1.1 Definitions

In Tableau, data fields are categorized into two types: Dimensions and Measures.

Dimensions

• Definition: Dimensions are fields that typically contain categorical data or attributes.
• Purpose: Used to group, categorize, or segment data.
• Display: Appears as blue pills when added to the view.
• Examples: Region, Customer Name, Product Category, State, City.

Practical Example:

• If you want to analyze Sales by Region, the "Region" field (Dimension) will segment or group the data into categories (e.g., East, West, North, South).

Measures

• Definition: Measures are fields that contain numerical data used for calculations and aggregations.
• Purpose: These fields can be summed, averaged, counted, or aggregated.
• Display: Appears as green pills when added to the view.
• Examples: Sales, Profit, Quantity, Discount.

Practical Example:

• If you analyze total Sales, the "Sales" field (Measure) will calculate the sum of Sales values.

1.2 Identifying Dimensions and Measures

In Tableau’s Data Pane (left side of the workspace):

• Dimensions are listed above the dividing line and are shown in blue.
• Measures are listed below the dividing line and are shown in green.

1.3 Default Aggregation for Measures

When you drag a Measure into the view, Tableau aggregates it by default. The most common aggregation is SUM (total value).

Aggregation	Description	Example
SUM	Total of all values	SUM(Sales)
AVG	Average of values	AVG(Profit)
COUNT	Number of rows	COUNT(Orders)
MIN / MAX	Smallest or largest value	MIN(Profit)
MEDIAN	Middle value	MEDIAN(Sales)

How to Change Aggregation

You can customize the aggregation for a Measure in Tableau:

1. Drag a Measure to the View:

   • Example: Drag Sales to the Rows or Columns shelf.

2. Change the Aggregation:

   • Right-click on the Measure in the view.
   • Select "Measure" > Choose the desired aggregation (SUM, AVG, COUNT, etc.).

Practical Example: Sales by Region

1. Drag Region to Rows:

   • "Region" is a Dimension and groups the data into categories.

2. Drag Sales to Columns:

   • "Sales" is a Measure and is aggregated as SUM(Sales) by default.

3. Result: Tableau creates a bar chart showing the total Sales for each Region.

Key Takeaways

• Dimensions segment data into categories (e.g., Region, Product Category).
• Measures are aggregated to calculate totals, averages, or other summaries.
• Blue Pills = Dimensions. Green Pills = Measures.

2. Discrete vs. Continuous Fields

Understanding the difference between Discrete and Continuous fields is essential for creating meaningful visualizations.

2.1 Discrete Fields

• Definition: Represent categorical or finite values.
• Display: Shown as blue pills in Tableau.
• Behavior: Create headers (categories) in a visualization.
• Examples: Customer Name, Region, Order ID, Years.

Practical Use Case:

• If you analyze Sales by Region, the Region field creates categories (e.g., East, West, South).

2.2 Continuous Fields

• Definition: Represent numeric or date values that are infinite or measurable.
• Display: Shown as green pills in Tableau.
• Behavior: Create axes with ranges in a visualization.
• Examples: Sales, Profit, Continuous Dates.

Practical Use Case:

• If you analyze Sales over time, the Sales field creates a continuous numeric axis.

2.3 Differences Between Discrete and Continuous Fields

Aspect	Discrete	Continuous
Representation	Blue pills	Green pills
Axis Type	Creates headers (categories)	Creates axes with numeric ranges
Examples	Region, Order ID, Year(Order Date)	Sales, Profit, Continuous Dates

2.4 Dates as Discrete vs. Continuous

Date fields in Tableau can behave as either Discrete or Continuous, depending on the analysis you want to perform:

Discrete Dates

• Treat dates as categories (e.g., Year, Month, or Day).
• Creates headers for each date part.

Example:

• Dragging Year(Order Date) creates categories like 2021, 2022, 2023.

Use Case: Comparing Sales year by year.

Continuous Dates

• Treat dates as a continuous range.
• Creates an axis with all dates evenly spaced.

Example:

• Dragging Order Date to the view creates a continuous date axis (e.g., 01/01/2023 to 12/31/2023).

Use Case: Plotting trends or changes over time (e.g., monthly sales trends).

Practical Example: Date Field in Line Chart

1. Drag Order Date to Columns:

   • Tableau treats it as Continuous by default (green pill).
   • Creates a continuous axis for dates.

2. Drag Sales to Rows:

   • Tableau creates a line chart showing Sales trends over time.

3. Switch to Discrete:

   • Right-click Order Date > Select "Convert to Discrete".
   • Dates now appear as categories (e.g., Year, Quarter).

Key Takeaways

• Discrete Fields (blue pills): Break data into categories or headers.
• Continuous Fields (green pills): Create axes for numeric or date ranges.
• Dates can behave as either Discrete (categorical) or Continuous (numeric range).

3. Aggregation in Tableau

3.1 What is Aggregation?

Aggregation refers to the process of summarizing data at a specific level of detail. When a Measure (numerical field) is placed into the view, Tableau automatically aggregates it based on the visualization's requirements.

For example:

• If you drag Sales into the view, Tableau aggregates it as SUM(Sales) by default.
• Other aggregations include AVERAGE, COUNT, MIN/MAX, and MEDIAN.

3.2 Types of Aggregations

Here is a breakdown of commonly used aggregations in Tableau:

Aggregation	Description	Example
SUM	Total of all values	SUM([Sales])
AVG	Average (mean) of values	AVG([Profit])
COUNT	Number of rows or non-null values	COUNT([Orders])
COUNTD	Count of distinct values	COUNTD([Customer ID])
MIN/MAX	Smallest or largest value	MIN([Profit]), MAX([Sales])
MEDIAN	Middle value in a sorted list	MEDIAN([Sales])

3.3 When Aggregation Occurs

• Tableau automatically aggregates Measures when they are placed on:
  • Rows Shelf
  • Columns Shelf
  • Marks Card

Example:

1. Drag Sales to the Rows shelf.
   • Tableau aggregates Sales as SUM(Sales) by default.
2. Drag Region to the Columns shelf.
   • Tableau displays the total Sales for each Region.

3.4 Customizing Aggregation

You can customize how Tableau aggregates a Measure:

1. Right-Click the Measure:
   • In the view or Data Pane, right-click the Measure.
2. Select “Measure”:
   • Choose the desired aggregation (SUM, AVG, COUNT, etc.).

Example: Calculate Average Sales instead of the default Sum.

• Right-click on Sales > Select Measure > Choose Average.

3.5 Custom Aggregations with Calculations

You can write custom aggregation calculations for more advanced insights.

Example: Calculate the Average Order Value (Sales divided by Count of Orders).

SUM([Sales]) / COUNT([Order ID])  

Steps:

1. Right-click in the Data Pane > Create Calculated Field.
2. Enter the formula above.
3. Drag the new calculated field into the view.

3.6 Aggregation and Level of Detail

Aggregations in Tableau depend on the Level of Detail (LOD) in the view. For example:

• If you group data by Region, Tableau calculates SUM(Sales) at the Region level.
• Adding another Dimension, like Product Category, changes the level of detail, and Tableau recalculates the aggregation.

Example:

1. Region + Sales → Tableau calculates total Sales by Region.
2. Region + Product Category + Sales → Tableau calculates total Sales by Region and Product Category.

4. Level of Detail (LOD) Expressions

4.1 What is Level of Detail (LOD)?

The Level of Detail (LOD) in Tableau defines the granularity at which Tableau performs calculations. By default, Tableau calculates aggregations at the level of detail in the view. However, with LOD Expressions, you can define calculations at a fixed, included, or excluded level of detail, regardless of the view.

4.2 Types of LOD Expressions

1. FIXED LOD

   • Aggregates data at a specific level of detail, ignoring the dimensions in the view.

   • Use Case: Calculate Sales by Region, regardless of other filters or dimensions.

   • Syntax:

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

   • Example: Total Sales for each Region remains fixed, even if you add Product Category to the view.

2. INCLUDE LOD

   • Aggregates data at a finer level of detail by including additional dimensions.

   • Use Case: Calculate Average Profit per City, even if the view only shows Region.

   • Syntax:

     { INCLUDE [City] : AVG([Profit]) }  
     

   • Example: If the view shows Region, this expression will include City to calculate the Average Profit for each City within the Region.

3. EXCLUDE LOD

   • Aggregates data while excluding specific dimensions in the view.

   • Use Case: Calculate total Sales excluding State, even if State is present in the view.

   • Syntax:

     { EXCLUDE [State] : SUM([Sales]) }  
     

   • Example: If the view includes Region and State, this expression calculates Sales at the Region level while ignoring State.

4.3 Practical Examples of LOD Expressions

Example 1: FIXED LOD

• Scenario: Calculate total Sales for each Region.

• Formula:

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

• Result:

  • Even if you add other Dimensions like City or Product Category, Sales will remain fixed at the Region level.

Example 2: INCLUDE LOD

• Scenario: Calculate the Average Profit per City within each Region.

• Formula:

  { INCLUDE [City] : AVG([Profit]) }  
  

• Result:

  • Tableau calculates Average Profit at a more granular level (City), even if the view only shows Region.

Example 3: EXCLUDE LOD

• Scenario: Calculate total Sales at the Region level while excluding State.

• Formula:

  { EXCLUDE [State] : SUM([Sales]) }  
  

• Result:

  • Tableau calculates Sales for each Region but ignores the State-level granularity in the view.

4.4 Why Use LOD Expressions?

• Greater Control: Perform calculations at specific levels of detail independent of the view.
• Flexibility: Calculate values like fixed totals, finer-level averages, or excluded aggregations.
• Efficiency: Avoid complex data manipulations in the source file and do everything within Tableau.

5. Data Granularity and Aggregation

5.1 What is Granularity?

Granularity refers to the level of detail in the data. It determines how detailed or summarized the data is when visualized.

• High Granularity: Data has a lot of detail (e.g., individual transactions, daily sales).
• Low Granularity: Data is summarized or aggregated (e.g., yearly or monthly sales).

The level of granularity affects how Tableau aggregates and displays the data.

5.2 Changing Data Granularity in Tableau

In Tableau, you can adjust the level of granularity by using date fields or dimensions.

Example: Changing Granularity with Date Fields

1. Drag a Date Field into the View:

   • Drag Order Date to the Columns Shelf.

2. Change the Date Aggregation:

   • Click on the dropdown arrow for the Date field.
   • Choose one of the options:
     • Discrete Levels: Year, Quarter, Month, Day (creates headers or categories).
     • Continuous Ranges: Continuous axis for Date values (e.g., Month-Year).

Impact on Aggregation

The level of granularity affects how Tableau summarizes data. For example:

• Yearly Aggregation: Fewer rows → Data is summarized at the year level.
• Daily Aggregation: More rows → Data is detailed at the day level.

Practical Example: Granularity and Aggregation

Scenario: You want to analyze Sales data over time.

1. Drag Order Date to Columns:

   • By default, Tableau aggregates the date field to Year(Order Date).

2. Drag Sales to Rows:

   • Tableau shows SUM(Sales) for each year.

3. Adjust Granularity to Month:

   • Click the dropdown arrow on Order Date > Select Month.
   • The view updates to show SUM(Sales) for each month.

4. Result:

   • Changing granularity from Year to Month increases the detail level.

5.3 Combining Granularity with Other Dimensions

You can add more dimensions to further control the level of detail.

Example:

1. Drag Order Date (Month) to Columns.
2. Drag Region to Rows.
3. Drag Sales to Text (Marks Card).

Result: Tableau shows Sales broken down by Month and Region.

• Each combination of Month and Region represents a more detailed level of granularity.

5.4 Best Practices for Granularity

1. Match Granularity to the Analysis Goal:

   • Use high granularity for detailed analysis (e.g., daily trends).
   • Use low granularity for summaries (e.g., yearly performance).

2. Be Aware of Performance:

   • High granularity (e.g., daily data) can slow performance for large datasets.

3. Test Different Levels:

   • Use Discrete and Continuous options for date fields to see which one suits the analysis.

6. Measures and Dimensions in Shelves

In Tableau, you place Dimensions and Measures on different shelves to control how the data is visualized. Each shelf serves a specific purpose.

6.1 Rows Shelf

• What It Does: Creates a horizontal axis or displays data rows.
• Used For: Adding Dimensions or Measures to organize data into horizontal groupings.

Examples:

1. Drag Region to Rows:
   • Creates rows for each Region (East, West, South, Central).
2. Add Sales to Text:
   • Displays the SUM(Sales) next to each Region.

6.2 Columns Shelf

• What It Does: Creates a vertical axis or displays data as columns.
• Used For: Adding Dimensions or Measures to organize data into vertical groupings.

Examples:

1. Drag Order Date to Columns:
   • Creates columns for each Year, Month, or Day based on the chosen granularity.
2. Drag Sales to Rows:
   • Creates a vertical axis for SUM(Sales), forming a bar or line chart.

6.3 Marks Shelf

The Marks Shelf controls the visual encoding of the chart, such as color, size, labels, and tooltips.

Marks Shelf Options

Option	Description	Example
Color	Adds color to distinguish categories.	Sales by Region (different colors).
Size	Adjusts the size of marks based on values.	Bubble chart sized by Profit.
Label	Displays text labels on marks.	Show SUM(Sales) on bar chart.
Tooltip	Displays additional information on hover.	Show Region, Sales in tooltips.

Practical Example of Marks Shelf

Scenario: Create a bar chart showing Sales by Region, with additional context.

1. Drag Region to Rows:
   • Tableau creates rows for each Region.
2. Drag Sales to Columns:
   • Tableau creates a bar chart showing SUM(Sales) for each Region.
3. Enhance the Chart:
   • Color: Drag Profit to the Color shelf to highlight regions with high or low Profit.
   • Label: Drag Sales to the Label shelf to show exact Sales values.
   • Tooltip: Add extra fields (e.g., Discount) to the Tooltip shelf.

Result: A bar chart with colored bars, Sales labels, and tooltips providing additional context.

6.4 Best Practices for Using Shelves

1. Use Rows and Columns Wisely:

   • Place Dimensions on Rows or Columns to group and organize the data.
   • Add Measures to display numerical values.

2. Maximize the Marks Shelf:

   • Use Color and Size to highlight key trends and patterns.
   • Add Labels to display important data points without overwhelming the chart.

3. Keep the View Clean:

   • Avoid adding too many fields to the Marks shelf to prevent clutter.

4. Use Tooltips Strategically:

   • Tooltips should provide extra insights, not repeat the chart’s main information.

7. Level of Detail (LOD) Expressions: Deep Dive and Examples

As discussed earlier, Level of Detail (LOD) Expressions allow you to perform calculations at different levels of detail, independent of what’s shown in the view. Let’s revisit each type of LOD and explore detailed examples.

7.1 FIXED LOD Expression

Definition:

The FIXED LOD aggregates data at a specific level of detail, ignoring other Dimensions in the view.

Use Case:

Calculate Sales by Region, regardless of other fields in the view.

Example 1: Total Sales by Region

• Formula:

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

• Steps:

  1. Create a Calculated Field with the formula above.
  2. Drag the Region field to Rows.
  3. Drag the FIXED LOD field to the view.

• Result: The total Sales for each Region will remain constant, even if you add another Dimension like State to the view.

Example 2: Unique Customer Count per Region

• Formula:

  { FIXED [Region] : COUNTD([Customer ID]) }  
  

• Result: Displays the distinct count of customers in each Region, regardless of other fields in the view.

7.2 INCLUDE LOD Expression

Definition:

The INCLUDE LOD performs aggregation at a finer level of detail by including additional Dimensions, even if they’re not in the view.

Use Case: Calculate the Average Profit per City within each Region.

Example: Average Profit per City

• Formula:

  { INCLUDE [City] : AVG([Profit]) }  
  

• Steps:

  1. Create the calculated field with the above formula.
  2. Add Region to Rows.
  3. Drag the INCLUDE LOD field into the view.

• Result:
  Tableau calculates the Average Profit for each City but aggregates it up to the Region level for display.

7.3 EXCLUDE LOD Expression

Definition:

The EXCLUDE LOD performs aggregation while excluding specific Dimensions from the calculation, even if they are present in the view.

Use Case: Calculate total Sales at the Region level, excluding State from the aggregation.

Example: Sales Excluding State

• Formula:

  { EXCLUDE [State] : SUM([Sales]) }  
  

• Steps:

  1. Create the calculated field with the formula above.
  2. Add Region and State to Rows.
  3. Add the EXCLUDE LOD field to the view.

• Result:
  Tableau calculates Sales at the Region level, ignoring the State dimension.

Summary of LOD Expressions

LOD Type	Purpose	Example
FIXED	Fixes aggregation at a specific level.	{ FIXED [Region] : SUM(Sales) }
INCLUDE	Adds finer-level detail to the aggregation.	{ INCLUDE [City] : AVG(Profit) }
EXCLUDE	Excludes specific dimensions from the aggregation.	{ EXCLUDE [State] : SUM(Sales) }

8. Data Granularity and Aggregation in Practice

8.1 Impact of Granularity on Aggregation

The level of granularity directly influences how Tableau aggregates the data.

Example: Sales Data

Granularity	Level of Detail	Aggregation
Yearly	Year(Order Date)	Total Sales per Year
Monthly	Month(Order Date)	Total Sales per Month
Daily	Day(Order Date)	Total Sales per Day

8.2 Changing Granularity for Analysis

1. Drag a Date Field to Columns:

   • By default, Tableau aggregates to Year.

2. Adjust Granularity:

   • Click the dropdown for the date field > Choose Month, Quarter, or Day.

3. Result:

   • Tableau recalculates the aggregation (e.g., Sales) at the selected granularity.

Practical Example: Daily Sales Trends

Scenario: Analyze the trend of Sales over time at the daily level.

1. Drag Order Date to Columns and select Day.
2. Drag Sales to Rows.
3. Tableau creates a line chart showing daily Sales trends.

9. Review of Key Tableau Concepts

Here’s a quick summary of the fundamental Tableau concepts:

Concept	Description	Example
Dimensions	Categorical fields used to group or segment data.	Region, Customer Name
Measures	Numeric fields used for calculations and aggregations.	Sales, Profit
Discrete	Categorical data that creates headers (Blue Pills).	Year(Order Date), Region
Continuous	Numeric or date data that creates axes (Green Pills).	Sales, Profit, Continuous Date
Aggregation	Summarizing data (SUM, AVG, COUNT, etc.).	SUM(Sales), AVG(Profit)
LOD Expressions	Custom calculations at specific levels of detail.	{ FIXED Region : SUM(Sales) }
Granularity	The level of detail in the data.	Yearly, Monthly, Daily trends

10. Final Best Practices for Understanding Tableau Concepts

1. Master Blue vs. Green:

   • Remember: Blue pills = Dimensions (Discrete), Green pills = Measures (Continuous).

2. Choose the Right Aggregation:

   • Use SUM for totals, AVG for averages, and COUNTD for distinct counts.

3. Adjust Granularity Carefully:

   • Match the granularity (Yearly, Monthly, Daily) to the purpose of your analysis.

4. Use LOD Calculations Wisely:

   • Use FIXED to control aggregation regardless of view filters.
   • Use INCLUDE for finer detail.
   • Use EXCLUDE to ignore certain dimensions.

5. Practice with Date Fields:

   • Switch between Discrete (Year, Month) and Continuous (Date Ranges) to understand their impact on the visualization.

6. Explore the Marks Shelf:

   • Leverage Color, Size, Label, and Tooltip to enhance the clarity of your charts.

Understanding Tableau Concepts (Additional Content)

1. View-Level Aggregation vs Data Source Aggregation

Why This Matters:

Many Tableau users confuse aggregation that occurs within Tableau’s view with pre-aggregated data from the source. This distinction often leads to double-counting errors or incorrect KPIs.

Key Concepts:

• Tableau performs aggregation in the view layer by default (after connecting to raw data).
• If your data source already includes aggregated data, such as summarized sales per region in Excel, Tableau may perform an additional layer of aggregation unless handled properly.

Example Use Case:

• You import a pre-summarized Excel sheet where each row shows Total Sales per Region.
• Dragging this "Sales" field into Tableau and aggregating with SUM(Sales) can lead to overcounting.

Exam Tip:

A question may ask:

"Why does your visualization show double the expected total Sales?"

Correct answer: The source data is already aggregated. Tableau added an additional layer of aggregation (SUM) over it.

Best Practice:

• Check your data granularity before aggregating in Tableau.
• Use "View Data" or preview the data to understand the level of detail in the source.

2. LOD Expressions vs Table Calculations – Conceptual Distinction

Why This Matters:

The exam may present a scenario and ask whether to use LOD Expressions or Table Calculations based on context. It is crucial to understand their timing, scope, and behavior.

Comparison Table:

Attribute	LOD Expression	Table Calculation
Execution Phase	Before aggregation (data layer)	After aggregation (view layer)
View Dependency	Not fully dependent on view structure	Highly dependent on the view
Cross-Sheet Reusability	Yes	No (tied to specific worksheet)
Common Use Cases	Fixed KPIs, Row-level control	Running Totals, Rank, Percent of Total
Syntax Examples	{ FIXED [Region] : SUM([Sales]) }	RUNNING_SUM(SUM([Sales]))

Scenario-Based Insight:

If you need to calculate "Total Sales by Region" regardless of what’s in the view → use an LOD expression.

If you want to calculate a "Cumulative total over months" → use a Table Calculation.

3. How to Determine the Current View’s Level of Detail (LOD)

Why This Matters:

Understanding LOD expressions isn’t just about writing them — it’s about knowing what the current view’s LOD is, so you can reason about how Tableau aggregates.

Key Principles:

• The combination of dimensions in the view defines the current LOD.
• Adding more dimensions increases granularity and changes the aggregation level.
• Tableau aggregates measures based on the dimensions present in Rows, Columns, Marks, Filters, etc.

How to Inspect:

• Go to: Analysis > View Data to examine what granularity Tableau is currently operating at.
• Observe the number of unique rows — it matches the dimensional breakdown in the view.

Example:

• If your view includes Region + Product, Tableau computes one row per Region-Product pair.
• Adding Customer ID would make the aggregation finer, potentially increasing row count.

4. LOD Conflicts in Dual-Axis Charts – Troubleshooting Tips

Why This Matters:

In complex visualizations (e.g., dual-axis charts), mixing fields with different LODs often causes alignment issues or inconsistent behavior.

Common Problem:

• One axis uses a FIXED LOD calculation (e.g., Region-level benchmark),
• The other axis displays data at a finer level (e.g., Product within Region),
• The result: one line shows stable values, the other fluctuates, but they do not align properly.

Solutions and Tips:

1. Ensure axis synchronization:

• Right-click on one axis > Synchronize Axis

2. Align dimensions:

• Add the same dimension (e.g., Region) to both Measures’ shelves (Marks cards) to align the context.

3. Control sort order manually:

• Use sort fields to ensure the visual order matches for both lines or bars.

4. Use calculated fields to "flatten" the LOD:

• If needed, convert FIXED LOD to a regular field aligned with the chart’s dimensions.

Exam Relevance:

You may be asked:

"A dual-axis chart is not displaying aligned values. What could be causing it?"

Correct answer: One axis is based on an LOD calculation that aggregates at a different level.

5. Controlling Summary Granularity: LOD vs Parameters vs Aggregated Fields

Why This Matters:

In advanced reporting, users often want to dynamically switch the granularity of a metric — such as toggling between Yearly, Quarterly, or Monthly summaries. Tableau allows this through parameter-driven logic and LOD expressions.

Three Techniques Compared:

1. Parameter + IF/CASE Logic (dynamic control)

• Create a parameter: Date Level = “Year”, “Quarter”, “Month”

• Use a calculated field:

  IF [Date Level] = "Year" THEN DATETRUNC("year", [Order Date])
  ELSEIF [Date Level] = "Quarter" THEN DATETRUNC("quarter", [Order Date])
  ELSE DATETRUNC("month", [Order Date])
  END
  

• Use this calculated date in your view

2. LOD Expressions for Static KPIs

• Build fixed-level aggregations:

  { FIXED [Customer ID] : AVG([Order Value]) }
  

• This is useful when you want KPI metrics that don’t change with the rest of the view.

3. Pre-Aggregated Calculated Fields

• Create new fields like SUM([Sales]) or AVG([Sales]) at specific group levels.
• Less flexible than LODs or parameters but easier for beginners.

Combined Strategy Use Case:

• Use a parameter to let the user pick the granularity
• Use CASE logic to choose which calculated field or LOD expression to use
• Result: a dynamic, user-driven, multi-granularity visualization

Exam Insight:

Expect a scenario like:

"How can you let users choose to see Sales by Year or by Quarter?"

Correct answer: Use a parameter combined with a calculated field that adjusts the date level.

Summary of Key Additions

Concept	Why It Matters	How It’s Tested
View-Level vs Source Aggregation	Prevents over-aggregation errors	Scenario questions involving inflated totals
LOD vs Table Calculations	Essential conceptual difference	Matching scenarios to method types
Understanding View LOD	Impacts aggregation and LOD usage	Analyze why numbers change after adding dimensions
LOD Conflict in Dual-Axis	Avoid misaligned visuals	Troubleshoot visual inconsistencies
Dynamic Summary Levels	Needed for user flexibility	Create parameter-controlled time aggregations