In Tableau, what can set actions and parameter actions do that a filter action cannot?
answer
- one writes a value, one writes membership
- the unselected rows can stay on screen
- calculations can read what the click set
- how do you keep the denominator?
- parameter holds exactly one thing
basics
~20 sThey write the clicked value into an object calculations can read: a parameter holds one value, a set holds membership. A filter action only removes rows, so it cannot drive a calculation, keep the unselected rows visible, or compare selection against the whole.
solid answer
~50 sA filter action can only narrow the target's rows. A **Change Parameter** action writes the selected mark's value into a parameter, and a **Change Set Values** action rewrites which members are in or out of a set. Because both parameters and sets can be referenced inside calculated fields, the selection becomes an input to logic rather than a subtraction of data — you can colour or label rows as selected versus other, compare the selection with the unfiltered total, or drive titles and reference lines from the click. Sets additionally hold many members at once and expose IN/OUT, which is how proportional brushing works: the selected marks stay highlighted and the rest remain visible so the reader sees the share of the whole. A parameter holds exactly one value, so it suits swapping a measure, a comparison baseline, or a dimension level.
code
text · 3 lines// Calculated field: sales for the customers selected on the map
SUM(IF [Selected Customers] THEN [Sales] END)
/ TOTAL(SUM([Sales]))go deeper
Be ready to recognize the names: a Change Parameter action puts the clicked value into a parameter, a Change Set Values action changes which members are in a set, and a filter action only removes rows.
Explain why calculations can read a parameter or a set but not an action filter, and give the shape of proportional brushing — selected members flagged while every row stays visible.
Show judgment about when the extra machinery pays: keeping the denominator, asymmetric drill, dynamic baselines. Acknowledge the re-query cost and the discoverability cost for the next author.
Own the standard for advanced interactivity: when a bespoke set-driven pattern is worth the maintenance burden versus reaching for a simpler design or moving the logic into the modelled layer everyone shares.
## The three ways a click can change a dashboard Tableau's dashboard actions include filter, highlight, navigation, URL, **Change Parameter** and **Change Set Values**. The first two act on what the target displays. The last two act on *state the workbook can compute with*, and that is the whole distinction. - A **filter action** removes rows from the target. The target's totals recompute over what is left, and the unselected rows are gone. - A **parameter action** writes the value of the field on the clicked mark into a parameter. A parameter is a single-value control, so the last click wins. - A **set action** changes which members are in a set. A set holds many members and every row is either IN or OUT of it. Selecting several marks puts all of them in. Both parameters and sets can be referenced inside calculated fields, on the Marks card, in filters, in titles and in reference lines. That is what a filter action cannot offer: the selection is data the workbook can reason about. ## Proportional brushing — the canonical set-action pattern The question *what share of total sales do the customers I just selected on this map represent?* cannot be answered with a filter action, because filtering to those customers destroys the denominator. With a set action it is straightforward: the map writes the selected customers into a set, and a bar chart shows two measures — sales for members of the set, and sales overall. The unselected rows stay on screen, so the reader sees the selection as a proportion of the whole rather than in isolation. The same mechanism supports asymmetric drill-down: a hierarchy where the reader expands only the branch they clicked, implemented by putting the clicked member into a set and using set membership inside the calculations that decide what level of detail to show. A filter action drills every branch or none. ## Parameter-action patterns Because a parameter holds one value, parameter actions suit interactions with a single subject: - **Comparison baseline** — click a region and every other region's bar becomes a difference against the clicked one. - **Dynamic titles and annotations** that name the selected member. - **Reference lines** positioned at the selected member's value. - **Measure or dimension swapping**, where the parameter feeds a calculation that returns a different field. Parameter actions run against a field on the clicked mark, and the parameter's data type must accept that field's values. The parameter is per-session state: two viewers of the same published dashboard do not affect each other. ## Sets versus parameters, concretely | | Parameter | Set | | --- | --- | --- | | Holds | one value | many members, IN/OUT per row | | Belongs to | the workbook, independent of any data source | one data source and one dimension | | Typical use | swap, baseline, threshold, dynamic title | brushing, membership flags, asymmetric drill | A set is defined against a specific dimension in a specific data source, which is also its limitation: it cannot span two sources the way a workbook-level parameter can. ## Costs These actions are not free. A calculation that reads a set or a parameter is evaluated by the data source like any other calculated field, so a set action still causes the target sheets to re-query when the calculations that depend on it change. The advantage is design freedom, not zero cost. They also make a workbook harder for the next author to read. A filter action is visible in Dashboard > Actions and its effect is obvious; a set action's effect is spread across calculated fields that reference `[Selected Customers]`, and someone who does not know the pattern will not find them. Name sets and parameters so the mechanism is discoverable, and keep the dependent calculations few. ## When a plain filter action is still right Most interactions want a filter action. If the reader's intent is *show me only these rows*, filtering is simpler, obvious in the actions dialog and easy to maintain. Reach for set and parameter actions when the interaction needs the unselected rows to stay visible, or needs the selection to feed logic — those are the two problems filter actions genuinely cannot solve.
- Why can't a filter action produce a proportional-brushing view?Because filtering removes the unselected rows, and proportional brushing needs them: the point is to show the selection as a share of the whole. Once the denominator is filtered away, any percent-of-total recomputes over the selection alone and always reads 100%. A set action keeps every row and only flags membership, so a calculation can compare members against the full data.
- What limits a parameter action compared with a set action?A parameter holds exactly one value, so the last click wins and multi-select is meaningless. That suits a baseline, a swap or a dynamic title, and it rules out anything about a group of selected members. Sets carry many members with an IN/OUT flag per row, but they are bound to one dimension in one data source, where a parameter is workbook-level and can be read from any source.
- What is the maintenance cost of building interactions from set and parameter actions?The effect stops being visible in the actions dialog. A filter action's behaviour is self-evident; a set action's behaviour lives in calculated fields that reference the set, scattered across sheets. The next author sees a click that changes colours for no apparent reason. Name the set and parameter for what the interaction means, keep the dependent calculations few, and document the pattern in the workbook.
A filter action throws away the parts of the picture you did not pick; a set action just marks them, so you can still see how big your piece is compared with the frame.
saying these in an interview costs you the question
- Saying a parameter can hold several selected members
- Assuming set actions avoid re-querying the target sheets
- Using a set action where a plain filter action would do
- Treating a set as workbook-level state independent of a data source
- Claiming filter actions can drive a calculated field directly