Resolving Filter and Aggregation Issues in Tableau

Resolving filter and aggregation issues is an essential skill for Tableau developers, data analysts, and business intelligence professionals. Filters control which data appears in a worksheet or dashboard, while aggregations summarize data using functions such as SUM(), AVG(), COUNT(), MIN(), and MAX(). When filters and aggregations interact unexpectedly, dashboards may display incorrect totals, percentages, rankings, or trends. Understanding Tableau's order of operations, aggregation levels, filter types, and calculation behavior helps analysts identify problems and produce accurate visualizations.

Tableau Training: Explore Tableau Training

Course Demo: Register for a Tableau Course Demo

1. Learning Objectives

After completing this topic, learners will be able to:

• Understand filters and aggregations in Tableau.
• Identify common filtering and aggregation problems.
• Differentiate dimension filters from measure filters.
• Understand extract, data source, context, dimension, measure, and table calculation filters.
• Understand Tableau's order of operations.
• Resolve incorrect totals, averages, percentages, and counts.
• Understand aggregate and non-aggregate calculation conflicts.
• Troubleshoot filter interactions with FIXED LOD expressions.
• Apply filters correctly in dashboards and published reports.
• Validate results using practical datasets and real-world examples.

2. What Are Filters in Tableau?

A filter restricts the data included in a worksheet, visualization, or dashboard. Filters help users focus on specific dates, regions, customers, product categories, sales values, and other conditions.

For example, a sales dashboard may contain records for several regions. A Region filter allows users to display only West region sales or compare selected regions.

Example

Suppose a dataset contains the following sales records:

The total sales across all records are 45,000. If the Region filter is set to West, the displayed total becomes 27,000.

Why Filters Are Important

• Focus on relevant data.
• Enable interactive dashboard analysis.
• Support comparisons between business segments.
• Reduce the amount of information shown in a view.
• Allow users to investigate trends and outliers.
• Support certain data access and reporting requirements when configured appropriately.

Important: A regular visualization filter is not automatically a data security control. Use appropriate data policies and permissions when restricting access to sensitive information.

3. What Is Aggregation in Tableau?

Aggregation is the process of summarizing multiple records into a single value. Tableau aggregates measures based on the dimensions and level of detail in the current visualization.

Common Aggregation Functions

Example: Total Sales

SUM([Sales])

This expression calculates total sales for the records represented by the current mark or group.

Example: Average Sales

AVG([Sales])

This expression calculates the average of the underlying sales values for the current level of detail.

Key concept: Aggregation depends on the visualization's level of detail. The same measure may display as a single grand total, a total for each region, or a total for each product and region.

4. Understanding Filter Types in Tableau

Tableau provides several filter types. Each type has a different role in determining which records or marks are included in a calculation or displayed in a visualization.

How to Add a Filter

1. Open a Tableau worksheet.
2. Drag the desired field to the Filters shelf.
3. Select the values, range, or condition to apply.
4. Confirm the filter settings.
5. To expose an interactive control, open the field's menu and select Show Filter when available.
6. Test the filter and verify the resulting values.

5. Understanding Tableau's Order of Operations

Tableau's order of operations determines the sequence in which different filters and calculations are evaluated. It is one of the most important concepts for troubleshooting unexpected filter results.

The broad logical sequence includes extract filters, data source filters, context filters, FIXED LOD expressions, applicable dimension filters, INCLUDE and EXCLUDE LOD expressions, measure filters, and table calculations. Table calculation filters are applied after the relevant table calculations are evaluated. Exact behavior can depend on the calculation type and view configuration.

Why the Order of Operations Matters

Suppose a worksheet displays total sales by product, and a user expects a FIXED calculation to change whenever a Region dimension filter changes. A FIXED LOD expression is evaluated before ordinary dimension filters, so the result may not respond to the Region filter as expected.

Example: FIXED LOD Expression

{ FIXED [Customer ID] : SUM([Sales]) }

This calculates sales per customer at the specified level of detail. An ordinary dimension filter does not necessarily change the FIXED result because FIXED calculations occur earlier in the order of operations than ordinary dimension filters.

Ways to Resolve Filter Order Problems

• Determine which calculation or filter is producing the unexpected result.
• Check whether the calculation uses FIXED, INCLUDE, or EXCLUDE.
• Consider whether the filter should affect the LOD calculation.
• Use a context filter when appropriate to make a dimension filter apply before a FIXED LOD expression.
• Review the requirements before changing the calculation type.
• Validate the result with multiple filter selections.

Best practice: Do not make a filter a context filter automatically. Context filters can affect performance, and the change should be justified by the intended calculation behavior.

6. Common Filter Issues in Tableau

Filter issues may cause a visualization to show too many records, omit expected records, display unexpected totals, or behave differently from another worksheet.

Common Problems

• A filter does not affect a particular worksheet.
• A filter displays fewer values than expected.
• A dashboard filter affects some charts but not others.
• A Top N filter returns unexpected members.
• A filter removes records needed for a calculation.
• A FIXED LOD calculation does not change after a filter is applied.
• A filter works in Tableau Desktop but behaves differently after publishing.
• A date filter excludes records because of date or date-time boundaries.

Step-by-Step Troubleshooting

1. Check the field used by the filter.
2. Verify the selected values, range, or condition.
3. Inspect the worksheet's Filters shelf.
4. Check whether the filter is applied to the intended worksheets.
5. Review dashboard filter actions and target sheets.
6. Examine the order of operations for calculations and filters.
7. Test the filter using a small worksheet with a simple table.
8. Compare the result with the source data.

7. Resolving Filters That Do Not Affect All Worksheets

One common dashboard issue occurs when a filter changes one chart but leaves other charts unchanged. This usually happens because the filter is scoped to selected worksheets or because the worksheets use different data sources or field relationships.

How to Fix It

1. Open the dashboard containing the filter.
2. Open the filter card's menu.
3. Select Apply to Worksheets.
4. Choose the appropriate option, such as selected worksheets or all worksheets using the relevant data source.
5. Check that the target worksheets use compatible fields or data sources.
6. Test the dashboard by selecting multiple filter values.

Example

A dashboard contains a Sales by Region chart, a Profit by Region chart, and an Orders by Region chart. If the Region filter affects only the sales chart, check its worksheet scope and whether the other charts are connected to the expected data source.

Important: Applying a filter to multiple worksheets does not guarantee that every worksheet will respond identically. Data source differences, field mappings, relationships, and filter configuration can affect the outcome.

8. Resolving Dimension Filter Problems

Dimension filters work with categorical fields such as Region, Category, Segment, Customer Name, and Product Name. They can use selected values, wildcard matching, conditions, or Top N settings.

Example: Filter by Region

To display West region sales, drag Region to the Filters shelf and select West.

Common Dimension Filter Issues

• The required value is missing from the filter list.
• The filter excludes expected categories.
• Similar text values appear as separate members.
• Trailing spaces or inconsistent spelling cause mismatches.
• A Top N filter returns a different result after other filters are applied.

Resolution Steps

1. Check the underlying field values.
2. Look for spelling differences, spaces, and inconsistent capitalization.
3. Confirm whether the filter is using selected values, wildcard, condition, or Top N.
4. Review any context filters that may change the available subset.
5. Check whether data source filters or extract filters have already excluded records.
6. Validate the selected members against the underlying data.

Example: Standardizing Text Values

If a source contains inconsistent text values, a calculated field may help standardize them:

UPPER(TRIM([Region]))

This converts text to uppercase and removes leading and trailing spaces. Use a standardized field for filtering only after checking how it affects existing business rules and categories.

9. Resolving Measure Filter Problems

Measure filters restrict marks based on numeric measures. They typically evaluate aggregated values, such as SUM(Sales), AVG(Profit), or COUNTD(Customer ID), at the level of detail represented in the view.

Example: Filter Products by Sales

Suppose the goal is to display products with total sales greater than 10,000.

1. Drag Product Name to Rows.
2. Drag Sales to Columns.
3. Drag Sales to the Filters shelf.
4. Select the appropriate aggregation and range or condition.
5. Set the lower limit to 10,000 if that is the intended threshold.
6. Validate the remaining products against their aggregated sales values.

Common Problems

• Filtering individual records when the requirement concerns totals.
• Using AVG instead of SUM, or vice versa.
• Applying the filter at an unintended level of detail.
• Using a threshold that does not match the business requirement.
• Confusing a measure filter with a table calculation filter.

Example Calculation

SUM([Sales]) > 10000

This Boolean expression tests whether the aggregated sales value exceeds 10,000 at the relevant level of detail. Depending on the worksheet and calculation setup, a direct measure filter may be more appropriate than creating a separate calculated field.

10. Resolving Aggregation Level Problems

Aggregation problems occur when a metric is calculated at a different level of detail than expected. A total may change when a dimension is added to a worksheet, or an average may differ from an independently calculated business metric.

Example: Total Sales

SUM([Sales])

This returns sales totals for the marks in the view. When Region is added to the view, Tableau calculates the total for each region instead of displaying only one overall total.

Example: Average Sales

AVG([Sales])

This calculates the average of the underlying sales values represented by the mark. It is not the same as calculating average sales per customer or average sales per region unless the data and level of detail make those definitions equivalent.

How to Troubleshoot Aggregation Problems

1. Identify the business definition of the metric.
2. Check which dimensions are present in the worksheet.
3. Inspect the aggregation assigned to each measure.
4. Compare the result with a known value from the source data.
5. Test the metric at different levels of detail.
6. Check whether joins or relationships affect the number of records represented.
7. Review the effects of filters and null values.

11. Understanding SUM, AVG, COUNT, and COUNTD

Choosing the wrong aggregation function is a frequent source of inaccurate reports.

Example: COUNT Versus COUNTD

Suppose a dataset contains five records but only three distinct customer IDs. COUNT(Customer ID) may return five if all five IDs are non-null, while COUNTD(Customer ID) returns three.

COUNT([Customer ID])
COUNTD([Customer ID])

Use COUNTD when the business question concerns unique customers rather than the number of records.

12. Understanding Incorrect Totals After Filtering

A total may change unexpectedly after applying a filter because the filter removes records before a particular calculation is evaluated, or because the metric is calculated at a different level of detail.

Example

Suppose total sales across all regions equal 45,000. A Region filter selects West, and the sales total becomes 27,000. This is expected if the metric is intended to reflect only the selected region.

However, a separate FIXED LOD field that calculates sales across a broader level of detail may continue to show values that include records outside the ordinary dimension filter.

Example FIXED LOD Calculation

{ FIXED : SUM([Sales]) }

This expression calculates a total across the source records available to the calculation, subject to earlier filters such as extract, data source, and context filters. It may not respond to a regular dimension filter.

Possible Solutions

• If the total should reflect the selected dimension filter, consider making that filter a context filter.
• Review whether the metric should be a FIXED LOD calculation at all.
• Consider a regular aggregate calculation when the intended result should follow the view's filter behavior.
• Compare the total before and after filtering using a simple worksheet.
• Document whether the dashboard should show filtered totals or overall totals.

Important: Overall totals that remain unchanged after filtering may be intentional. Confirm the requirement before modifying the calculation.

13. Resolving Average Calculation Issues

Average calculations often produce unexpected values because an average of individual records is different from an average of pre-aggregated groups.

Example: Average Transaction Value

AVG([Sales])

This calculates the average sales value across the records represented in the view.

Example: Average of Regional Totals

Suppose three regions have sales totals of 10,000, 20,000, and 70,000. The unweighted average of these regional totals is 33,333.33. This is not the same as the average sales value of all individual transactions.

Common Causes of Incorrect Averages

• Using an average when the requirement is a weighted average.
• Calculating the average of group totals instead of individual records.
• Including or excluding null values unexpectedly.
• Applying a filter that changes the records contributing to the average.
• Using a duplicated dataset after a join.

Resolution Steps

1. Define what one observation represents.
2. Determine whether the required result is an average of records, groups, or a weighted average.
3. Check the number of records contributing to the calculation.
4. Review null handling and filters.
5. Validate the result with a manual calculation on a small dataset.

14. Resolving Duplicate Records and Join-Related Aggregation Problems

Duplicate records can inflate SUM() and COUNT() results. These issues often arise when tables are joined at different levels of detail or when a dataset contains multiple records for the same business entity.

Example

Suppose an order with sales of 1,000 appears twice after a join. SUM(Sales) may report 2,000 instead of 1,000 if both joined rows are counted.

Common Causes

• A one-to-many join duplicates measures from the one side.
• The source contains duplicate business records.
• The join uses incomplete keys.
• Tables have different granularities.
• Relationships or joins are configured incorrectly for the intended analysis.

Resolution Steps

1. Identify the intended grain of each source table.
2. Inspect the join keys and relationship configuration.
3. Compare record counts before and after combining tables.
4. Check whether the business key uniquely identifies a record.
5. Validate SUM(), COUNT(), and COUNTD() against source totals.
6. Use an appropriate data model or pre-aggregation when required.

Best practice: Do not use COUNTD() or an arbitrary aggregation to hide duplicated records. Resolve the data modeling problem or clearly define the metric first.

15. Resolving Top N Filter Issues

Top N filters display the highest-ranked dimension members according to a measure. They may return unexpected results when other filters, context filters, or ranking calculations affect the candidate records.

Example: Top 5 Products by Sales

1. Place Product Name in the worksheet.
2. Open the Product Name filter.
3. Navigate to the Top tab.
4. Select the option to display the top five products by field.
5. Choose SUM(Sales) as the ranking measure.
6. Apply the filter and verify the displayed products.

Why Top N Results May Change

• The ranking measure uses the wrong aggregation.
• The filter evaluates within a different subset than expected.
• A context filter changes which records are considered.
• The source contains ties at the ranking boundary.
• A table calculation is being used instead of a dimension Top N filter.

Resolution Tips

• Confirm the ranking measure and aggregation.
• Check the relevant filter order.
• Determine whether the Top N should apply before or after a region or category restriction.
• Test the results in a simple table sorted by the measure.
• Check how ties should be handled by the reporting requirement.

16. Resolving Quick Table Calculation and Filter Issues

Table calculations, such as running totals, ranks, and percent of total, operate on the values in the visualization. Their behavior can change when dimensions are added, removed, filtered, or reordered.

Example: Percent of Total

Tableau's quick table calculation can calculate the percent of total for the values in the view.

SUM([Sales]) / TOTAL(SUM([Sales]))

This formula calculates a mark's sales divided by the total evaluated by the TOTAL() table calculation in the view. The result depends on the table calculation configuration.

Common Problems

• Percentages do not add up to 100% as expected.
• The denominator changes after adding a dimension.
• Filtering a category changes the displayed percentages.
• Rankings restart unexpectedly.
• A table calculation uses the wrong addressing or partitioning.

Resolution Steps

1. Open the table calculation settings.
2. Check the Compute Using configuration.
3. Inspect addressing and partitioning dimensions.
4. Confirm whether percentages should be calculated from all data or only the visible subset.
5. Review whether the filter acts before or after the table calculation.
6. Test with a simple worksheet and known values.

Important: A table calculation filter can hide marks after the table calculation has been computed. Therefore, the remaining visible percentages may not add up to 100% if the calculation was evaluated over a larger set of marks.

17. Resolving FIXED LOD and Context Filter Issues

FIXED LOD expressions calculate values at a specified granularity and follow a different evaluation order from ordinary dimension filters. This distinction can create confusing results when users expect a filter to change an LOD value.

Example: Customer Sales

{ FIXED [Customer ID] : SUM([Sales]) }

This calculation returns sales per customer based on the records included at the applicable stage of Tableau's order of operations.

Problem

A user selects the West region, but the FIXED customer sales value continues to include sales from other regions.

Solution

1. Confirm whether the calculation is a FIXED LOD expression.
2. Check whether Region is an ordinary dimension filter.
3. If the calculation should respect Region, test making the Region filter a context filter.
4. Alternatively, reconsider whether a standard aggregate or another LOD expression better represents the required metric.
5. Validate results for multiple regions and customers.

Context filters change the evaluation context for relevant downstream operations, including FIXED LOD calculations. They should be used carefully because their effect can also change Top N results and performance.

18. Resolving Filter Problems with Null Values

Null values can influence filter results, aggregation functions, and displayed categories. A null is not the same as zero or an empty string.

Example: Identify Missing Sales

IF ISNULL([Sales]) THEN
    "Missing Sales"
ELSE
    "Available Sales"
END

This calculated field classifies records according to whether Sales is null.

Example: Replace Null with Zero

ZN(SUM([Sales]))

ZN() returns zero when the numeric expression is null. Use it only when zero is a valid interpretation of the missing result.

Common Null-Related Filter Issues

• Null values are not included in a selected set of members.
• A filter excludes records with missing dimension values.
• SUM() or AVG() does not produce the expected result because of null inputs.
• Missing values are mistaken for zero values.
• A join introduces nulls because matching records are unavailable.

Resolution Steps

1. Inspect the source data for null values.
2. Check whether the nulls originate from the source, a join, or a calculation.
3. Determine whether null values should be displayed, excluded, or classified separately.
4. Use an appropriate filter or calculation to handle them.
5. Revalidate totals and averages after changing the logic.

19. Resolving Date Filter Issues

Date filters may use relative dates, date ranges, discrete date parts, or continuous date values. Problems can arise from the wrong date field, incorrect date types, or confusion between dates and date-time values.

Common Date Filter Problems

• Recent records are missing from the view.
• A date range excludes the expected final day.
• A relative date filter shows a different period than expected.
• The source date is stored as text.
• Date-time values contain times that affect range boundaries.

Resolution Steps

1. Confirm which date field is being filtered.
2. Verify the field's data type.
3. Check whether the filter uses a date part, range, or relative date.
4. Inspect the minimum and maximum source dates.
5. Review time components if the source uses date-time values.
6. Test the filter with a few known records around the boundary.

Example: Filter Current Year

One way to create a current-year Boolean filter is:

YEAR([Order Date]) = YEAR(TODAY())

Place the calculated field on the Filters shelf and select TRUE. Confirm that the source date field is valid and that the intended definition of the current year matches the reporting requirement.

20. Understanding Filter Actions in Dashboards

Filter actions allow users to select marks in one worksheet and filter one or more target worksheets. They are useful for interactive dashboards, drill-down analysis, and exploring related information.

Example

A dashboard contains a map of sales by region and a chart of product sales. Selecting a region on the map filters the product chart to show products for that region.

How to Configure a Filter Action

1. Open the dashboard.
2. Select Dashboard > Actions.
3. Add a Filter action.
4. Choose the source worksheet and target worksheet or worksheets.
5. Choose the selection trigger, such as selecting a mark.
6. Configure how the target view handles clearing the selection.
7. Test the action with different marks and selections.

Common Issues

• The source worksheet does not trigger the action.
• The target worksheet is not selected.
• Fields used to pass the filter are incompatible.
• Clearing the selection leaves an unexpected view.
• The action filters only a subset of the intended dashboard.

Troubleshooting Tips

• Verify the source and target worksheets.
• Check the action's selected fields and filter mappings.
• Test the action with a single known mark.
• Confirm the clearing-selection behavior.
• Review any existing dashboard filters that may interact with the action.

21. Resolving Filter Performance Issues

Filters can affect workbook performance, especially when a dashboard contains many worksheets, complex calculations, large datasets, or high-cardinality fields.

Common Performance Problems

• Dashboard filters take a long time to update.
• Quick filters contain a very large number of values.
• Changing a filter triggers several expensive queries.
• Context filters are used unnecessarily.
• Many worksheets perform similar calculations against large datasets.

Best Practices for Better Performance

• Keep only necessary filters visible on the dashboard.
• Limit high-cardinality filter controls when possible.
• Use relevant extract filters or data source filters when reducing the available dataset is appropriate.
• Use context filters only when they improve the required evaluation behavior or query performance.
• Reduce unnecessary worksheets and expensive calculations.
• Review data modeling and joins.
• Use Tableau's performance recording tools to identify slow queries and calculations.
• Test performance using realistic data volumes.

Note: The best filter strategy depends on the data source, workbook design, and query workload. A context filter is not automatically faster than an ordinary filter.

22. Practical Project: Troubleshooting a Sales Dashboard

Project Objective

Build a Tableau sales dashboard and resolve common filter and aggregation issues.

Sample Dataset

Task 1: Create a Total Sales Measure

SUM([Sales])

Display total sales by region and validate the grand total against the dataset.

Task 2: Create a Profit Ratio

IF SUM([Sales]) = 0 OR ISNULL(SUM([Sales])) THEN
    NULL
ELSE
    SUM([Profit]) / SUM([Sales])
END

Format the result as a percentage and verify the numerator and denominator.

Task 3: Add a Region Filter

1. Drag Region to the Filters shelf.
2. Select the required regions.
3. Show the filter control.
4. Test East, West, and all regions.
5. Confirm that the displayed totals respond as expected.

Task 4: Add a Category Filter

Create a category filter and apply it to the relevant dashboard worksheets. Confirm that all intended charts respond to the selection.

Task 5: Create a Top 3 Product View

Use a Top N filter to display the three highest-selling products. Verify the ranking measure and aggregation.

Task 6: Diagnose a FIXED LOD Issue

{ FIXED : SUM([Sales]) }

Add this calculation to a worksheet with a Region filter. Observe whether the value changes. If the requirement is to make it respond to the Region filter, test using Region as a context filter and validate the new behavior.

Task 7: Validate the Dashboard

• Check sales totals by region.
• Check profit ratio calculations.
• Verify that filters affect the intended worksheets.
• Confirm Top N results.
• Test the FIXED LOD calculation.
• Inspect null values and unexpected records.
• Document each issue and its resolution.

Expected Outcome

The completed dashboard should provide accurate sales and profit metrics, predictable filter behavior, correct ranking results, and consistent calculations across worksheets.

23. Best Practices for Filters and Aggregations

• Define the metric first: Decide whether the business question requires a sum, average, count, distinct count, or another measure.
• Understand the data grain: Know what one row represents before aggregating measures.
• Check filter order: Consider how filter types interact with LOD and table calculations.
• Use context filters intentionally: Apply them when their evaluation behavior is needed.
• Validate totals: Compare dashboard metrics against source data or trusted reports.
• Investigate duplicates: Check joins, relationships, and record granularity before changing aggregations.
• Handle nulls deliberately: Do not automatically convert missing values to zero.
• Use appropriate filter scope: Ensure filters affect the intended worksheets.
• Test boundary cases: Validate date ranges, zero values, nulls, ties, and empty filter selections.
• Monitor performance: Avoid unnecessary filter controls and expensive calculations.
• Document the business logic: Explain why a particular filter or aggregation is used.
• Revalidate after publishing: Test published dashboards and data sources in the target environment.

24. Common Mistakes to Avoid

25. Interview Questions and Answers

Q1. What is a filter in Tableau?

Answer: A filter restricts the data available to a worksheet or visualization according to selected values, ranges, conditions, or other criteria.

Q2. What is aggregation in Tableau?

Answer: Aggregation summarizes records using functions such as SUM(), AVG(), COUNT(), MIN(), and MAX().

Q3. What is the difference between a dimension filter and a measure filter?

Answer: A dimension filter typically restricts categorical members, while a measure filter typically restricts marks based on numeric measure values at the relevant level of detail.

Q4. What is Tableau's order of operations?

Answer: It is the sequence in which Tableau evaluates filters and calculations. It matters because a calculation may be evaluated before or after a particular filter.

Q5. Why might a FIXED LOD calculation not respond to a dimension filter?

Answer: FIXED LOD expressions are evaluated before ordinary dimension filters. Making the dimension filter a context filter can cause it to affect the FIXED calculation, when that matches the requirement.

Q6. What is the difference between COUNT() and COUNTD()?

Answer: COUNT() counts non-null field values, while COUNTD() counts distinct non-null values.

Q7. Why do sales totals sometimes increase after joining tables?

Answer: A join may duplicate records when tables have different levels of detail or the join keys do not uniquely identify the intended records. The data model and grain should be checked.

Q8. Why might an average change after adding a dimension?

Answer: Adding a dimension changes the level of detail of the view and may change how records are grouped. The analyst should verify whether the required metric is an average of records, groups, or a weighted average.

Q9. How can you make a dashboard filter affect multiple worksheets?

Answer: Use the filter card's Apply to Worksheets option and select the intended worksheets. Also verify data source compatibility and any dashboard filter actions.

Q10. What is a context filter?

Answer: A context filter creates a primary subset of data for applicable downstream filtering and calculations. It can affect FIXED LOD calculations and Top N behavior.

Q11. What is a table calculation filter?

Answer: It filters marks based on results after the relevant table calculations are evaluated. The visible marks may therefore represent only part of the set used by a table calculation.

Q12. How do you troubleshoot incorrect percentages?

Answer: Verify the numerator, denominator, aggregation, level of detail, filter order, and table calculation configuration. Compare the results against known values.

Q13. How do you troubleshoot a Top N filter?

Answer: Check the dimension, ranking measure, aggregation, filter order, context filters, and ties. Validate the ranking in a simple sorted worksheet.

Q14. How can filters affect performance?

Answer: Filters can trigger additional queries, process large value lists, or interact with expensive calculations. Performance recording and careful dashboard design help identify bottlenecks.

Q15. What is the best way to validate an aggregation?

Answer: Define the metric, confirm the data grain, inspect the aggregation, compare the result with source data, and test the calculation under different filter selections.

26. Practical Exercises

1. Create a worksheet displaying total sales by region.
2. Add a Region filter and validate the sales total for each selection.
3. Create a Category filter that affects multiple worksheets.
4. Compare SUM(Sales) with AVG(Sales) and explain the difference.
5. Compare COUNT(Order ID) with COUNTD(Customer ID).
6. Create a Top 5 products filter based on SUM(Sales).
7. Build a FIXED LOD calculation and test its behavior with an ordinary dimension filter.
8. Convert a relevant dimension filter to a context filter and compare the results.
9. Create a percent-of-total table calculation and investigate how filtering affects the displayed percentages.
10. Investigate a dataset with duplicate records and explain how they affect totals.
11. Create a dashboard filter action that links two worksheets.
12. Document at least three filter or aggregation issues, their causes, and their resolutions.

27. Troubleshooting Checklist

• Have you selected the correct field for the filter?
• Are the filter values, ranges, and conditions correct?
• Does the filter affect the intended worksheets?
• Are dashboard filter actions configured correctly?
• Have you reviewed Tableau's order of operations?
• Is the correct aggregation function being used?
• Does the metric match the data's level of detail?
• Are duplicate records or join issues inflating totals?
• Are null values handled appropriately?
• Do Top N filters use the intended measure and aggregation?
• Have you checked context filters and FIXED LOD behavior?
• Have you checked table calculation addressing and partitioning?
• Have you tested different filter selections and edge cases?
• Have you compared the result with the source data?
• Have you validated the published dashboard and performance?

28. Official Tableau Learning Resources

• Filter Data from Your Views — learn about filtering data in Tableau worksheets.
• Tableau's Order of Operations — understand how Tableau evaluates filters and calculations.
• Level of Detail Expressions — understand FIXED, INCLUDE, and EXCLUDE calculations.
• Aggregation of Measures — learn how Tableau summarizes measures.
• Filter Actions — learn how to filter worksheets interactively from a dashboard.
• Tableau Help and Support — access additional Tableau documentation and support resources.

29. Quick Revision

30. Conclusion

Resolving filter and aggregation issues in Tableau requires a clear understanding of how data is filtered, how measures are summarized, and how calculations interact with the view's level of detail. Most issues can be diagnosed by checking filter scope, aggregation functions, data grain, join behavior, and Tableau's order of operations.

For more advanced troubleshooting, pay close attention to FIXED LOD expressions, context filters, Top N filters, and table calculations. Always test the results with known values, multiple filter combinations, and realistic data before publishing a dashboard. This approach helps create accurate, interactive, and dependable Tableau reports.

Explore Tableau Training: Explore Tableau Training

Register for a Tableau Course Demo: Register for a Tableau Course Demo