33 Interactive Tableau Dashboards with Filters and Actions

33.1 Why Interactive Dashboards Matter

A static dashboard answers one question at a glance; an interactive dashboard answers any question the audience cares to ask.

A printed PDF or static image of a dashboard delivers a fixed answer. The same dashboard rendered in Tableau, with filters and actions, becomes an instrument the audience can drive — narrowing to a region, drilling into a customer, switching between measures, comparing periods, all without involving the analyst.

The standard practitioner reference on dashboard design is The Big Book of Dashboards by Steve Wexler et al. (2017), which catalogues real-world business dashboards and the interactive patterns behind them. Practical Tableau by Ryan Sleeper (2018) is the corresponding deep guide to building those interactions in Tableau itself.

For a visualisation-focused book, this chapter is where Tableau’s distinctive interaction model comes together. Filters, parameters (covered in Chapter 31), and Actions are what turn a worksheet into a self-service analytical tool.

33.2 The Tableau Dashboard Workspace

flowchart TD
    DW["Tableau Dashboard"]
    DW --> S["Sheets<br>Drag worksheets onto<br>the dashboard canvas"]
    DW --> O["Objects<br>Text, Image, Web Page,<br>Blank, Navigation, Buttons"]
    DW --> L["Layout<br>Tiled or Floating<br>Horizontal or Vertical<br>Containers"]
    DW --> Si["Sizing<br>Fixed, Range,<br>Automatic"]
    DW --> A["Actions<br>Filter, Highlight, URL,<br>Set, Parameter,<br>Go to Sheet"]
    DW --> D["Device Layouts<br>Desktop, Tablet, Phone"]
    style DW fill:#e3f2fd,stroke:#1976D2
    style S fill:#fce4ec,stroke:#AD1457
    style O fill:#fff3e0,stroke:#EF6C00
    style L fill:#fff8e1,stroke:#F9A825
    style Si fill:#e8f5e9,stroke:#388E3C
    style A fill:#ede7f6,stroke:#4527A0
    style D fill:#f3e5f5,stroke:#6A1B9A

A Tableau dashboard is composed in the Dashboard view (third icon in the worksheet tabs at the bottom). The left-hand panel offers:

Sheets — the worksheets in this workbook, ready to drag onto the canvas.
Objects — Text, Image, Web Page, Blank, Horizontal container, Vertical container, Download button, Extension, Show/Hide button, Navigation button.
Tiled / Floating toggle — controls whether the next object snaps into the layout grid (Tiled) or sits freely above (Floating).

The right-hand panel shows the Layout tree of dashboard objects and lets the analyst lock dimensions, set padding, and inspect the container hierarchy.

33.3 Dashboard Sizing and Layout

Dashboard Sizing Modes

Mode	Behaviour	When to Use
Automatic	Adjusts to the viewer’s window	Quick prototyping; rarely production-ready
Fixed Size	Designed at a specific pixel size; scales the same on every screen	Most production dashboards; ensures the layout the designer intended
Range	Resizes within a min and max bound	Adapts to a small range of screen sizes without breaking

The default for production work is Fixed Size — typically 1366×768 (laptop) or 1280×800 (compact). Without this, the dashboard reflows on different screens and the carefully tuned layout (KPI strip across the top, primary panel upper-left, etc.) is lost.

For multi-device support, Tableau’s Device Designer lets the analyst create separate Desktop, Tablet, and Phone layouts of the same dashboard, each with its own size and visible objects. Tableau Server / Cloud serves the layout matching the user’s device.

33.3.1 Tiled versus Floating

Tiled objects snap into the dashboard’s grid; they push and resize as siblings change. Floating objects sit above the grid at fixed pixel coordinates; they do not displace anything.

Best practice:

Tiled by default — most worksheets, KPI cards, and container layouts should be tiled.
Floating sparingly — for overlays, hover tooltips, parameter controls in unusual positions, or branded watermarks.

A dashboard with everything floating is one move away from a layout disaster on resize.

33.3.2 Containers

Horizontal and Vertical containers are the structural primitives of dashboard layout. They group objects so they resize, align, and pad together. A useful pattern:

One outermost vertical container for the whole dashboard.
A horizontal container at the top for the KPI strip.
A horizontal container below for the primary panel and a sidebar.
A vertical container in the sidebar for filter cards and parameter controls.

The Layout tree on the right reveals the container hierarchy. Naming containers (right-click → Edit Name) makes complex layouts maintainable.

33.4 Filters in Tableau

Filters are the most familiar interactive control. Tableau provides several layers, each with its own scope.

The Layers of Filtering

Filter Type	Scope	When to Use
Data Source Filter	The entire workbook	Security and global restrictions (this region only, current year only)
Context Filter	Promoted filter; runs first; other filters operate on its result	Performance for very large data; needed for FIXED LOD subqueries
Worksheet Filter	Single worksheet	A worksheet-level filter that should not affect siblings
Quick Filter / Filter Card	User-facing on dashboard	Standard interactive filter
Filter Action (cross-filter)	One worksheet’s selection filters another	Click-to-filter interactivity in dashboards

The hierarchy matters: Data Source Filters apply to everything; Context Filters apply before all worksheet filters; Worksheet Filters apply to the worksheet they are on. Misordering can produce wrong results.

33.4.1 Apply Filter to Worksheets

A common confusion: a Quick Filter dropped on a dashboard initially affects only the worksheet it came from. To make it affect more:

Right-click the filter card → Apply to Worksheets → All Using This Data Source (most common) or Selected Worksheets (for surgical control).

The Apply-to-Worksheets setting is the single most-asked Tableau dashboard question. Mature workbooks set it deliberately for every filter card.

33.5 Dashboard Actions

Actions are interactive behaviours triggered by the user. To configure: Dashboard → Actions → Add Action, choose the action type, source sheet, target sheet, fields, and run-on behaviour (Hover, Select, Menu).

The Six Action Types

Action	Behaviour	Common Use
Filter Action	Source selection filters target visuals	Click a region bar to filter the rest of the dashboard
Highlight Action	Source selection highlights matching marks in target	Click a customer to highlight that customer across views
URL Action	Opens a URL using fields from the selected mark	Click a product to open its catalogue page
Set Action	Selection changes the membership of a Tableau Set	Dynamic top-N, in/out highlighting, sub-selection
Parameter Action	Selection changes a Parameter’s value	Click a year to set the year parameter (covered in Chapter 31)
Go to Sheet (Navigation Action)	Selection navigates to another sheet	Click a row to drill into a detail view

The default and most important Action is the Filter Action: clicking on a mark in one worksheet filters the others. Almost every interactive dashboard uses it.

33.5.1 Run On — When the Action Fires

Each Action specifies when it fires:

Hover — fires when the cursor hovers over a mark; fast but can be jumpy.
Select — fires when the user clicks; the standard choice.
Menu — fires when the user clicks and chooses from a tooltip menu; useful when several actions are possible from the same mark.

The choice depends on the audience and the precision required. For an executive dashboard, Select is almost always the right answer; Hover is more common in analyst-facing exploration tools.

33.6 Interactive Design Patterns

A handful of recurring interactive patterns drive most production dashboards:

Master-Detail (Drill Down): A summary worksheet on top filters a detail worksheet below. Click a region; the detail shows transactions in that region.
Cross-Filter (Brush): Multiple worksheets on a dashboard mutually filter each other when any one is clicked. Click a category, the bar chart and the map both update.
Highlight-Without-Filter: Selection highlights but does not filter, so the user can compare the selected element with the rest in context.
Show / Hide Container: A button toggles the visibility of a container. Useful for filter panels that pop out only when needed, or for swapping between two views in the same canvas region.
Tabs and Navigation: A row of Navigation buttons at the top lets the user move between dashboard pages (Summary, Region Detail, Customer Detail).
Tooltip Visualisations (viz in tooltip): Hovering a mark shows a small chart of that mark’s history in the tooltip; powerful when the tooltip would otherwise just repeat the mark’s value.
Set Actions for Top-N: Click a region; a Set updates to that region’s top customers; the rest of the dashboard adapts.

33.7 Mobile and Device-Specific Dashboards

For audiences consuming dashboards on tablets and phones, Tableau’s Device Designer allows three layouts per dashboard:

Desktop — the primary layout, typically 1366×768 fixed.
Tablet — adapted layout, 1024×768.
Phone — vertically stacked, 375×667.

To configure: in the Dashboard pane, click + Phone or + Tablet and Tableau scaffolds a layout you can adjust. Hide objects that do not fit a small screen, change container orientation from horizontal to vertical, and resize text appropriately.

Tableau Server / Cloud automatically serves the right layout based on the user’s device. The dashboard URL is the same; only the rendering changes.

33.8 Performance Considerations for Interactive Dashboards

Interactivity is only useful if it is fast. A dashboard whose filters take five seconds to apply will not be used.

Use Extracts rather than Live for analytical dashboards.
Limit the number of filters on a dashboard; ten is usually plenty.
Avoid Quick Filters with thousands of distinct values; switch to a wildcard search filter or a parameter.
Use Context Filters to reduce the working set before downstream filters and LOD subqueries.
Watch for cross-filter cascade where one Filter Action triggers a chain of expensive queries; consider Highlight Actions where filtering would be wasteful.
Profile with Performance Recording: Help → Settings and Performance → Start Performance Recording. Tableau records every query and renders a dashboard of the slowest steps when the recording stops.
Reduce visual complexity: A dashboard with twenty marks per visual is faster than one with twenty thousand.

33.9 Best Practices for Interactive Design

Default view stands alone: The first thing the user sees should be useful, even if they never click.
Discoverability: Interactive features should be obvious; users should not have to be told that clicking does anything.
Consistent interaction grammar: If clicking a region filters in one panel, clicking should filter (not highlight) in others.
Reset path: Provide a clear way to return to the default view (a Reset button using a Show/Hide container or a Clear All Filters action).
Smooth transitions: Tableau’s animations help the eye track changes; turn them on (Format → Animations).
Visible state: At any moment, the user should know which filters are applied; show filter values prominently or echo them into the dashboard title via a parameter.
Mobile checks: Test the Phone layout on a real phone, not the design preview.

33.10 Common Pitfalls

Filter Card Without Apply-to-Worksheets: A Quick Filter only affects its origin worksheet, leaving the rest unfiltered; users see partial state.
Hidden Cross-Filter: A Filter Action that the user cannot see triggers; the dashboard appears to behave erratically.
Floating Layout Sprawl: Everything floating; resizing the dashboard breaks every position.
No Default Filter State: Dashboard opens with no filters set; the user faces an empty or overwhelming view.
Slow Quick Filter on High Cardinality: A filter card with 50,000 customer names; the dashboard freezes.
Action Run-on Hover for Critical Actions: Hover-fired filter actions are jumpy and unintentional.
No Mobile Layout: Audiences consuming on phones see the desktop layout, unreadable.
Action Cascade Loops: Action A triggers worksheet B, B’s filter triggers another action; loops are difficult to debug.
Mixing Tiled and Floating Without Reason: A dashboard with tiled and floating objects layered haphazardly is impossible to maintain.

33.11 Illustrative Cases

A Master-Detail Sales Dashboard

A regional sales lead’s dashboard has a master view of region performance and a detail view of stores within the selected region. Clicking a region in the master view filters the detail view via a single Filter Action. The user navigates from the macro level to the micro without leaving the dashboard.

A Customer-360 with Cross-Filtering

A customer-analytics dashboard shows a scatter of customers, a bar chart of revenue by segment, and a map of customer locations. Clicking on any view filters the other two. The user explores by clicking; no separate filter card is needed.

A Phone Layout for Field Staff

A retail sales force consumes its weekly performance dashboard on phones during morning store visits. The desktop layout has six panels; the phone layout has only the three highest-priority KPIs, vertically stacked. The phone-rendered dashboard fits on a single scroll.

33.12 Hands-On Exercise: Building a Comprehensive Interactive Tableau Dashboard

Aim: Build a complete interactive sales dashboard for Yuvijen Stores that exercises filters, parameters, Filter Actions, Highlight Actions, and Set Actions, plus a phone layout for mobile consumption. This is the primary Tableau dashboard hands-on referenced by the syllabus.

Deliverable: A Tableau workbook (.twbx) with a Desktop and Phone layout, four worksheets, six interactive elements, and a one-page reference describing the interactivity.

33.12.1 Step 1 — The Sample Data and Worksheets

Use the same sales.csv from the previous chapters (with order_id, order_date, customer_id, product, category, region, sales, profit, quantity).

Build four worksheets first:

KPI Tiles — four KPI cards (Total Sales, Total Profit, Profit Margin, Customer Count) using BAN-style Big Number visuals with sparkline tooltips.
Region Map — filled map of India with SUM(Sales) colouring each state.
Category Bar — sorted horizontal bar of SUM(Sales) by category.
Trend Line — line chart of SUM(Sales) by month, with a small target reference line.

Each worksheet is built in isolation first; the dashboard composes them in Step 2.

33.12.2 Step 2 — Compose the Dashboard with Containers

Click New Dashboard. Set size to Fixed → Desktop (1366×768).
Drag a Vertical container onto the canvas. This is the outermost container.
Inside it, drag a Horizontal container at the top — for the KPI strip.
Drop the four KPI worksheets into the horizontal container.
Below, drag another Horizontal container for the main row.
Inside, drag the Region Map on the left and a Vertical container on the right.
Inside the right vertical container, drop the Category Bar on top and the Trend Line below.
At the bottom of the dashboard, add a Text object for the data refresh time and source.

The four-zone Gutenberg layout is now set: KPI strip on top, primary panel upper-left (the map), supporting panels on the right.

33.12.3 Step 3 — Add Filter Cards

On the Trend Line worksheet, drag Order Date to Filters. Right-click → Show Filter to expose the filter card on the dashboard.
Right-click the filter card → Apply to Worksheets → All Using This Data Source.
Drag the filter card into the right vertical container above the Category Bar.
Repeat for Region: drag a filter card and apply to all worksheets.

The dashboard now has two visible global filters.

33.12.4 Step 4 — Add a Filter Action (Click Region to Filter Everything)

Dashboard → Actions → Add Action → Filter…
Source sheet: Region Map. Target sheets: Category Bar, Trend Line, KPI Tiles. Run on: Select.
Source field: Region. Target field: Region (all source fields, in this case).
Clearing the selection: Show all values.
OK.

Now clicking on a state in the map filters the rest of the dashboard. Clicking again clears.

33.12.5 Step 5 — Add a Highlight Action

Dashboard → Actions → Add Action → Highlight…
Source: Category Bar. Target: all sheets in dashboard. Run on: Hover.
Selected fields: Category.

Hovering on a category in the bar chart highlights matching marks across the map and trend line, giving the user a quick comparison of one category against the rest.

33.12.6 Step 6 — Add a Parameter and Parameter Action

Create a parameter Selected Year (Integer, list of 2024, 2025, 2026; default 2026).
Create a calculated field Year Filter:
```
YEAR([Order Date]) = [Selected Year]
```
Drag Year Filter to Filters on every worksheet, set to True.
Dashboard → Actions → Add Action → Change Parameter…
Source: Trend Line. Source field: YEAR(Order Date). Target parameter: Selected Year. Run on: Select.

Clicking a year on the trend line now sets the parameter, and every worksheet filters to that year.

33.12.7 Step 7 — Add a Set Action for Top Customers

Create a Tableau Set called Highlighted Customers from the customer dimension (right-click customer_id → Create → Set; pick any default member to start with).
Drag the set to the Marks card → Color on a customers worksheet (build a small new sheet for this if needed).
Dashboard → Actions → Add Action → Change Set Values…
Source: Category Bar. Target set: Highlighted Customers. Run on: Select.

Clicking a category now updates the set’s membership to all customers in that category, who become highlighted in any visual that uses the set.

33.12.8 Step 8 — Build the Phone Layout

In the Dashboard pane, click + Phone.
Tableau scaffolds a default phone layout. The layout is initially Custom and editable.
Toggle the visibility of objects on the phone layout — keep the four KPI tiles vertically stacked, then the Trend Line below, hide the Region Map and Category Bar (or move them to a second screen accessed by a Navigation button).
Resize text to a phone-readable size (16–20 pt for headlines).
Test on a real phone via Tableau Mobile or by reducing browser window to 375 px wide.

33.12.9 Step 9 — Best-Practice Polish

Add a Reset Filters button using a Show/Hide container with a Clear action.
Echo the active filters into the dashboard title using parameter and filter references.
Turn on Format → Animations so transitions are smooth.
Add a footer with Last refreshed, Data source, Owner contact.
Document the interactivity in a small text block: Click a region to filter; hover a category to highlight; click a year to switch the period.

33.12.10 Step 10 — Connect to the Visualisation Layer

The hands-on illustrates the complete shift from visualisation as artefact to visualisation as instrument:

A static version of these four charts would answer four questions and end there.
The interactive dashboard answers any combination of region, year, category, and segment the user cares to ask, on the same one-page canvas.
The phone layout extends the same instrument to the field staff who actually need the answers.

The technical work in this hands-on — containers, filters, six action types, device layouts — is the operational form of every dashboard principle covered in Module 2. Tableau is the tool; the principles are the design.

Files and Screen Recordings

Tableau workbook (yuvijen-interactive-dashboard.twbx), the source sales.csv, and screen recordings of each step including the Filter Action, Highlight Action, Parameter Action, Set Action, and Phone Layout will be embedded here.

Summary

Concept	Description
Foundations
Why Interactive Dashboards Matter	A static dashboard answers one question; an interactive dashboard answers any question the audience asks
Dashboard Workspace
Dashboard Workspace	Dashboard view composed in the third tab type with sheets, objects, layout, and actions
Sheets Pane	Worksheets in this workbook ready to drag onto the canvas
Objects Pane	Text, Image, Web Page, Blank, Containers, Buttons, Extensions, Show/Hide
Layout Pane	Tree of dashboard objects with locks, padding, and container hierarchy
Layout: Tiled, Floating, Containers
Tiled Layout	Objects snap into the dashboard's grid; push and resize as siblings change
Floating Layout	Objects sit above the grid at fixed pixel coordinates; do not displace anything
Horizontal Container	Structural primitive grouping objects to resize, align, and pad together horizontally
Vertical Container	Structural primitive grouping objects to resize, align, and pad together vertically
Sizing and Device Design
Automatic Sizing	Adjusts to the viewer's window; quick prototyping but rarely production-ready
Fixed Sizing	Designed at a specific pixel size; scales the same on every screen
Range Sizing	Resizes within a min and max bound; adapts to a small range of screens
Device Designer	Lets the analyst create separate Desktop, Tablet, and Phone layouts of the same dashboard
Filters
Data Source Filter	Filter on the entire workbook; security and global restrictions
Context Filter	Promoted filter that runs first; needed for FIXED LOD subqueries
Worksheet Filter	Filter on a single worksheet that should not affect siblings
Quick Filter	User-facing filter card on the dashboard
Filter Action (Cross-Filter)	Filter Action that filters target visuals from a source selection
Apply to Worksheets	Right-click filter card setting that determines which worksheets the filter affects
Action Types
Filter Action	Source selection filters target visuals; default and most important action type
Highlight Action	Source selection highlights matching marks in target without filtering them
URL Action	Opens a URL using fields from the selected mark
Set Action	Selection changes the membership of a Tableau Set
Parameter Action	Selection changes a Parameter's value
Go to Sheet Action	Selection navigates to another sheet
Run-On Behaviour
Run On Hover	Action fires on hover; fast but jumpy; rarely the right choice for filters
Run On Select	Action fires on click; the standard choice for most actions
Run On Menu	Action fires when the user chooses from a tooltip menu; useful when several actions are possible
Interactive Design Patterns
Master-Detail Pattern	Master worksheet on top filters detail worksheet below; click region to see stores
Cross-Filter Brush Pattern	Multiple worksheets mutually filter each other when any one is clicked
Highlight-Without-Filter Pattern	Selection highlights but does not filter so the user can compare in context
Show Hide Container Pattern	A button toggles the visibility of a container; pop-out filter panels
Tabs and Navigation Pattern	Row of Navigation buttons that move between dashboard pages
Viz in Tooltip Pattern	Hovering shows a small chart of the mark's history in the tooltip
Set Actions for Top-N	Click a region to update a Set whose membership becomes that region's top customers
Mobile Layouts
Desktop Layout	Primary 1366 by 768 layout for desktop consumption
Tablet Layout	Adapted layout for tablets, typically 1024 by 768
Phone Layout	Vertically stacked layout for phones, typically 375 by 667
Performance
Use Extracts	Use Extracts rather than Live for analytical dashboards
Limit Filter Count	Ten filters on a dashboard is usually plenty
Avoid High-Cardinality Quick Filters	Switch to wildcard search filter or parameter for thousands of distinct values
Context Filters for LOD	Use Context Filters to reduce the working set before LOD subqueries
Cross-Filter Cascade	One Filter Action triggering expensive query chains; consider Highlight instead
Performance Recording	Help, Settings and Performance, Start Performance Recording for query timing
Best Practices
Default View Stands Alone	First view should be useful even if the user never interacts
Discoverability	Interactive features should be obvious; clicking should look clickable
Consistent Interaction Grammar	If clicking filters in one panel it should filter in all panels
Reset Path	Provide a clear way to return to the default view via Reset button or action
Smooth Transitions	Format Animations on so transitions help the eye track changes
Visible State	User should always know which filters are applied
Mobile Checks	Test the Phone layout on a real phone, not the design preview
Common Pitfalls
Filter Card Without Apply-to-Worksheets	Pitfall of a Quick Filter that only affects its origin worksheet leaving the rest unfiltered
Hidden Cross-Filter	Pitfall of a Filter Action that the user cannot see triggering and producing erratic behaviour
Floating Sprawl	Pitfall of everything floating so resizing breaks every position
No Default Filter State	Pitfall of opening with no filters set and presenting an overwhelming view
Slow Quick Filter on High Cardinality	Pitfall of a filter card with thousands of distinct values freezing the dashboard
Hover for Critical Actions	Pitfall of hover-fired filter actions being jumpy and unintentional
No Mobile Layout	Pitfall of audiences consuming on phones seeing the desktop layout, unreadable
Action Cascade Loops	Pitfall of action chains where Action A triggers B which triggers C
Mixing Tiled and Floating Without Reason	Pitfall of tiled and floating objects layered haphazardly making the dashboard unmaintainable