Tableau Parameters, Filters and Actions in Databricks AI/BI Dashboards
September 9, 2026
In Databricks AI/BI, Tableau's filters, parameters and actions collapse into three mechanisms: field filters that act on dataset results, parameters substituted into dataset SQL as :name, and cross-filtering or drill-through between visuals built on the same dataset. The first decision on every dashboard is filter on a field or filter on a parameter.
A field filter acts on the resolved dataset result. A parameter is substituted into the query text before it runs. Almost every difference below follows from those two sentences; the docs behind them were read in September 2026.
Where each Tableau control lands in Databricks AI/BI
| Tableau | Databricks AI/BI | Note |
|---|---|---|
| Quick filter | Field filter widget | Six types, at global, page or widget scope |
| Context or data source filter | Widget-level filter, or a WHERE clause in the dataset | Widget-level values are fixed by the author |
| Relative date filter | Date range picker, relative mode | now-30d/d, re-evaluated each run |
| Parameter inside a calculation | Dashboard parameter written :name | String, Date, Date and Time or Numeric |
| Parameter plus CASE to swap a measure | Dashboard variable | Added June 4, 2026; works with metric views |
| Filter action | Cross-filtering | Visuals on the same dataset only |
| Go to Sheet action | Drill-through | Right-click, then Drill to a target page |
Field filter or parameter: the first decision
Databricks publishes its own comparison of the two.
| Behavior | Field filter | Parameter |
|---|---|---|
| Where it acts | On the resolved result, in a CTE at the end of the query | Substituted into the query at runtime |
| Performance | Typically faster; small results filter in the browser | The query reruns whenever the value changes |
| Versatility | Not usable in subqueries or custom conditional logic | Usable in subqueries, conditional logic, or to change query structure |
| Filter types | Six, including text entry and a range slider | Four: single and multiple values, date picker, date range |
A quick filter on a dimension becomes a field filter, and field filters cascade by default, so one selection narrows what the others offer. A parameter that changed what the query did, rather than which rows survived it, stays a parameter.
How a Tableau parameter is written in Databricks SQL
A dashboard parameter is a named parameter marker in the dataset query, so a threshold typed into a Tableau calculation becomes a value the query reads at runtime. Set its default in the Data tab: that is what viewers see before touching a control, unless the filter widget carries a default of its own.
Three Tableau habits need exact syntax. A range parameter creates two markers, so the predicate reads WHERE order_date BETWEEN :date_param.min AND :date_param.max OR :date_param IS NULL. A parameter accepting several values is read with WHERE array_contains(:region_param, region) OR :region_param IS NULL, and multiple selections have to be enabled on the parameter or the query errors. A parameter that named a table or column maps to the IDENTIFIER clause: SELECT * FROM IDENTIFIER(:catalog || '.' || :schema || '.' || :table).
Tableau's dynamic parameter, whose list refreshes from a field, becomes a query-based parameter: a second dataset returns the values, and one filter widget binds field and parameter. Give that list its own dataset; if it also feeds a chart, a viewer's pick filters that chart too.
The measure-switching pattern, a parameter plus a CASE calculation, has a purpose-built home. A dashboard variable groups fields so viewers can swap which one a visualization shows. Databricks says it replaces pairing IDENTIFIER with a parameter, because variables work with metric views and keep each field's formatting.
Parameters exist one layer below the dashboard as well. A Unity Catalog metric view can define its own parameters and is then called as a table-valued function, as in catalog.schema.metric_view(discount => 0.15), with a dashboard parameter passed in. One limit and one requirement are documented: a parameterized metric view cannot be materialized, and querying one needs compute running Databricks Runtime 18.2 or above. Defaults have their own rule: once one parameter carries a default, every parameter after it needs one too.
What happens to filter, highlight and URL actions
Tableau's six action types do not map one to one. A filter action becomes cross-filtering: clicking a bar filters every other visualization built on the same dataset. A dashboard whose filter actions crossed data sources has a modeling task ahead of it, not a wiring task. Since September 3, 2026, filters, selections and parameters carry across to widgets on datasets joined by a dashboard relationship, in Public Preview. Line, combo and area charts joined the cross-filtering list on June 11, 2026, though the chart list on the filters page has not been updated to match, so confirm behavior on your own dashboard.
A Go to Sheet action that opened a detail view becomes drill-through: the viewer picks Drill to and a page, and every visualization there on the same dataset is filtered by the selection. Multi-selection across multiple categorical dimensions, multiple quantitative dimensions, or multiple date-binned temporal values is not yet supported.
Go to URL becomes the Link action on a table or pivot column, where the cell value substitutes into a templated URL through {{@}}. Highlight, Change Parameter and Change Set Values actions are the gap: the docs describe no equivalent, and do not say they are impossible either.
What defaults, the Apply button and bookmarks change for viewers
Filter defaults apply when the dashboard refreshes without a selection, and the default is All. Filters apply instantly unless the dashboard is switched to With Apply Button, which lets viewers set several values before anything reruns: what a Tableau dashboard carrying eight quick filters wants.
State travels in the URL as f_<page-name>~<widget-name>=<filter-value>, so a bookmarked Tableau link keeps an equivalent, and editors can save named filter combinations as shared bookmarks, up to 10 per dashboard as of September 2026.
What Antares does with parameters and actions
One Tableau parameter often holds two jobs in a workbook: a threshold inside a calculation on one sheet, a Top N control on another. Only usage shows the split, which is why a BI migration tool inventories parameters and actions before converting anything. The free Analyzer does that pass on metadata alone, deterministically, and lists which workbooks carry parameters and actions.
Where the target is unambiguous, the Converter handles it. Where it is not, it is flagged for a person rather than guessed: a filter on the wrong side of the query changes the number without changing the picture. Tableau to Databricks AI/BI is shipped, and the Converter runs as SaaS or inside your own environment. Try a sample conversion to see what it produces.
What a viewer is allowed to see is a separate mechanism, on row-level security to Unity Catalog, and the order of the work is on the migration guide. For Power BI: parameters to Power BI and actions to drillthrough. Sources: Tableau's parameter documentation and Databricks' guide to dashboard filters.
← Back to the Tableau to Databricks Migration guide
Related Migration Resources
Frequently asked questions
What is the Databricks AI/BI equivalent of a Tableau parameter?
A dashboard parameter, written in the dataset query as a named parameter marker such as :region, with a String, Date, Date and Time or Numeric type. Bind it to a filter widget so viewers can change it. A parameter that only switched which measure a chart showed is better rebuilt as a dashboard variable.
Should I filter on a field or on a parameter in a Databricks AI/BI dashboard?
Databricks describes field filters as typically faster: they apply to the resolved dataset result without modifying the query, and small results are filtered in the browser. Choose a parameter when the value has to sit inside the query, for example in a subquery, in conditional logic, or before a join.
What happens to Tableau filter, highlight and URL actions?
Filter actions become cross-filtering, which is automatic between visuals built on the same dataset, and since September 3, 2026 carries across datasets joined by a dashboard relationship, in Public Preview. A Go to Sheet action becomes drill-through to a target page. A Go to URL action becomes the Link action on a table or pivot column, where the cell value fills a templated URL. Highlight, Change Parameter and Change Set Values actions have no equivalent described in the Databricks documentation.
Do Databricks metric views support parameters?
Yes. A metric view can define its own parameters and is then called as a table-valued function, with arguments passed by name or position, and a dashboard parameter can be passed into that argument and bound to a filter widget. One documented limit and one requirement: a parameterized metric view cannot be materialized, and querying one needs Databricks Runtime 18.2 or above.