I’m experiencing a frustrating issue with dashboard filters after publishing to Tableau Server. In Desktop, everything works perfectly - my dashboard filter actions propagate correctly to all linked worksheets. However, after publishing to Server (tab-2023.1), the worksheet filter linkage breaks completely.
The dashboard has three worksheets showing sales by region, product category, and time period. When I select a region in the main filter, it should update all three worksheets, but on Server only the first worksheet updates.
Filter Action Settings:
Source: Dashboard Filter
Target Worksheets: All Using Related Data Sources
Clearing Selection: Show All Values
This is impacting our executive reporting accuracy. Has anyone encountered this server publishing behavior issue?
This is typically a data source relationship issue. When you publish, Tableau Server treats each data source independently unless they’re explicitly related. Check your dashboard filter action configuration - specifically the ‘Target Sheets’ setting. You might need to use ‘Selected Fields’ instead of ‘All Fields’ to ensure proper field mapping. Also verify that the field names are identical across all data sources (case-sensitive).
I’ve solved this issue multiple times and it usually comes down to three specific areas you need to address systematically.
Dashboard Filter Actions: First, completely remove your existing filter action and recreate it with these exact settings:
Action Type: Filter
Source Sheet: [Your filter source]
Run action on: Select
Target Sheets: [Explicitly list each worksheet]
Clearing Selection: Leave the filter
Target Filters: Selected Fields only
Worksheet Filter Linkage: The key issue is that Server handles worksheet dependencies differently than Desktop. Go to each target worksheet individually and verify:
- Remove any existing filters on the Region_Name field
- Ensure no context filters are interfering
- Check that each worksheet’s data source is using the SAME published data source (not separate embedded extracts)
- Verify field mapping by right-clicking Region_Name → Describe to confirm field types match
Server Publishing Behavior: This is the critical piece most people miss. When you publish, go to your workbook settings on Server and:
- Check ‘Workbook Performance Recording’ to see which worksheets are actually receiving filter events
- Verify your server version supports cross-worksheet filtering (should be fine on 2023.1)
- Clear the server cache for your workbook: Server Settings → Cache → Delete cached data
- Test with ‘Show Sheets as Tabs’ temporarily to isolate whether it’s a dashboard container issue
The most common root cause I’ve found is when worksheets use slightly different data source connections even though they appear identical. Publish a single unified data source first, then ensure ALL worksheets connect to that exact published source rather than embedded copies. This ensures filter actions propagate correctly.
After making these changes, republish the entire workbook (not just refresh) and test immediately before any caching occurs. Let me know if this resolves your reporting accuracy issues.
I’ve seen similar behavior with filter actions after publishing. First thing to check - are all your worksheets using the same data source connection on the server? Even if they use the same data in Desktop, the server connections might be treated as separate instances. Go to the Data menu and verify the connection details match exactly across all worksheets.
Had this exact problem last month. The issue was that my filter action was set to ‘All Using Related Data Sources’ but the relationships weren’t properly defined on the server side. Try this: Edit your filter action and explicitly select each target worksheet individually rather than using the automatic selection. Also, make sure you’re using the same field for filtering across all sheets - sometimes calculated fields with the same name can cause mismatches.