In Tableau, how does a dashboard filter action differ from a highlight action?
answer
- one changes the query, the other changes the paint
- what happens to the target's totals?
- context preserved versus context removed
- dimmed marks are still marks
- eight targets, eight sets of queries
basics
~10 sA Tableau filter action removes non-matching rows from the target sheets, which re-queries them and changes their totals and axes. A highlight action keeps every mark and only emphasizes matching ones, dimming the rest.
solid answer
~50 sBoth are configured under Dashboard > Actions with a source sheet, a trigger (hover, select or menu) and target sheets, but they do different things to the target. A **filter action** passes the selected field values to the targets as a filter: rows that do not match disappear, each target sheet issues new queries, and axes, totals and reference lines all recompute against the smaller data. A **highlight action** changes nothing about what is queried — the target keeps all of its marks, the matching ones stay saturated and the rest are dimmed. Choose highlight when the point is *where does this sit within the whole*, because context is preserved; choose filter when the point is *show me only this*. A common design uses highlight for peer comparison charts and filter for a detail table beneath them.
go deeper
Be ready to say that filtering removes marks from the other sheets while highlighting keeps them and dims the non-matching ones, and to point at the funnel icon as the quick way to create a filter action.
Explain the mechanics: filter actions re-query each target so totals, axes and reference lines recompute; highlight actions only repaint existing marks. Know the hover, select and menu triggers.
Demonstrate design judgment. Decide per target whether the reader needs comparison context or a narrowed detail set, split one interaction into two actions with different target lists, and manage the query cost.
Own the interaction contract across a dashboard suite: which sheets are allowed to drive others, how drill-through between dashboards is standardized, and how much re-query cost per click the platform can absorb at your concurrency.
## The shared plumbing Dashboard actions in Tableau are defined under Dashboard > Actions (or from the caret menu of a sheet). Every action, whatever its type, has: - one or more **source sheets** the interaction starts from, - a **trigger**: run on **Hover**, on **Select**, or on **Menu** (a link in the tooltip), - **target sheets**, - a field mapping: **All Fields** (match on every field the two views share) or **Selected Fields** (an explicit source-field to target-field mapping). The types differ in what they do to the targets: Filter, Highlight, Go to URL, Go to Sheet, Change Parameter, Change Set Values. ## What a filter action does A filter action takes the dimension values on the mark you interacted with and applies them as a filter on the target sheets. Select a bar for the West region and every target sheet is now restricted to West. The consequences are the ones interviewers probe: - **The targets re-query.** Each target worksheet sends new queries to its data source. Eight targets means eight sets of queries per click, which is the usual root of a sluggish dashboard. - **Aggregates change.** Totals, averages, percent-of-total table calculations, reference lines, trend lines and forecasts all recompute over the filtered rows, because they are computed after filtering. - **Axes rescale.** With Automatic axes, filtering to one small category can make a chart look dramatically different from its unfiltered self. Fixing axis ranges is the usual counter-measure when that flicker is confusing. - **Marks disappear.** The reader loses the comparison set; they can no longer see how the selection compares with its peers. - **The empty-target case must be configured.** What happens when the user deselects is a separate setting on the action, and the default is not always what you want. A filter action behaves like a dimension filter on the target sheet. That matters for one classic surprise: a FIXED level-of-detail calculation is computed before dimension filters, so a value produced by one can appear not to respond to the click at all unless the filtered field is added to context. ## What a highlight action does A highlight action leaves the target's data alone. Every mark the target had is still drawn; marks whose values match the source selection stay at full colour and the rest are dimmed. Nothing is filtered away, so totals, axes, reference lines and table calculations are unchanged, and the reader keeps the full comparison set on screen. Because it operates on marks that are already rendered, highlighting feels instantaneous compared with filtering. The requirement is that the target view actually contains the field being matched on — in the view or on the Marks card — otherwise there is nothing to match and nothing highlights. Highlighting is also available without an action at all, through the highlighter control on a discrete field, which is often the simpler answer when only one sheet is involved. ## Choosing between them Ask what question the interaction answers. - *"How does this one compare with the others?"* — highlight. Removing the others destroys the comparison. - *"Show me only the rows behind this bar."* — filter, usually into a detail table or a secondary chart. - *"I want both."* — a common pattern is highlight across the peer charts and filter only the detail sheet, configured as two actions from the same source with different target lists. ## Configuration details worth knowing The funnel icon on a worksheet in a dashboard — **Use as Filter** — is a shortcut that generates a filter action running on Select from that sheet to every other sheet on the dashboard, matching on All Fields. It is convenient and it is also how dashboards accidentally become slow and over-coupled: every sheet re-queries on every click. Opening Dashboard > Actions and narrowing the target list is the standard cleanup. Run-on-Hover feels responsive for highlight actions and is usually a mistake for filter actions, because merely moving the mouse across a chart triggers query storms and makes the dashboard feel jumpy. Run on Menu is the gentlest trigger: nothing fires until the user clicks a link in the tooltip, which suits expensive targets and drill-through to another dashboard. Finally, a filter action is not the same thing as a filter card. A filter card is a control the reader manipulates directly; an action is an interaction driven by clicking a mark on another sheet. They can conflict — a target sheet can carry both, and the reader sees the intersection of the two.
- A filter action fires but a FIXED calculation in the target sheet does not change. Why?Action filters behave like dimension filters on the target, and Tableau computes FIXED level-of-detail expressions before dimension filters are applied. The FIXED value is therefore calculated over the unfiltered rows and looks frozen. Adding the filtered field to context promotes it ahead of the FIXED computation, which makes the value respond — at the cost of the target rebuilding its context each time.
- What does the Use as Filter funnel icon on a dashboard worksheet actually create?A filter action that runs on Select, uses that worksheet as its source, targets every other sheet on the dashboard, and matches on All Fields. It is fine for a small dashboard and a liability on a large one, because every click re-queries every sheet. The usual fix is to open Dashboard > Actions and narrow the target list to the sheets that genuinely need filtering.
- When is Run on Hover a bad trigger?For anything that re-queries. A hover-triggered filter action fires as the mouse crosses the chart, so casual mouse movement produces a stream of queries and a dashboard that flickers and lags. Hover is reasonable for highlight actions, which only repaint already-rendered marks. For expensive targets or drill-through to another dashboard, prefer Menu, which requires a deliberate click in the tooltip.
Filtering is turning the lights off in every room except one; highlighting is leaving the lights on everywhere and pointing a spotlight at one corner.
saying these in an interview costs you the question
- Saying highlight actions filter the target's underlying data
- Assuming a filter action leaves totals and axes unchanged
- Using Use as Filter everywhere without narrowing targets
- Setting a filter action to Run on Hover for responsiveness
- Confusing a filter card the user drives with an action-driven filter