Tableau Migration Actions Drillthrough

Tableau Actions to Power BI: Drillthrough, Cross-Filtering, and Navigation

July 28, 2026

The first thing to know is that the default is reversed. In Tableau, nothing happens between sheets until someone creates an action. In Power BI, visuals on a page cross-filter and cross-highlight each other out of the box, and the work is switching that off where it is unwanted. So converting Tableau actions is partly building features and partly deleting behaviour nobody asked for.

Tableau action types in Power BI

Tableau actionWhat it doesPower BI equivalent
FilterUses one view to filter anotherCross-filtering, already on by default
Filter to a detail sheetOpens a focused view of one itemDrillthrough page
HighlightDims all other marksCross-highlighting
Go to URLLinks to an external page or fileButton or column with a Web URL action
Go to SheetNavigates within the workbookPage navigation button
Change ParameterSets a parameter from a markNo equivalent, see parameters
Change Set ValuesRewrites a set from a selectionNo equivalent, see sets
Action running on hoverReveals detail without clickingReport page tooltip

The default is the opposite, so start by subtracting

By default, visualizations on a report page cross-filter and cross-highlight the others. Turn on Edit interactions in the Format menu and every other visual gains three icons: filter, highlight, and none. Set them per pair of visuals, and the choices are saved with the report so consumers see what you designed.

One constraint is documented and worth memorising, because it decides layouts: line charts, scatter charts and maps can only be cross-filtered, never cross-highlighted. A Tableau dashboard whose highlight action targeted a line chart cannot be reproduced literally, and the honest conversion is a filter with the difference explained to users, not a workaround that half-works.

Filter actions: cross-filter or drillthrough?

Tableau filter actions cover two jobs that Power BI separates. When the target sits on the same dashboard, the equivalent is cross-filtering and there is usually nothing to build. When the action opened a different sheet showing detail for one item, the equivalent is drillthrough.

A drillthrough page carries drillthrough filter fields that determine what it shows, and Power BI adds a back button automatically. Users reach it by right-clicking a data point or through a button whose action is set to Drillthrough. Three details save time later: the drillthrough field has to be present in the source visual for the menu entry to appear, the field must not be aggregated in that visual, and cross-report drillthrough works only in the Power BI service, between reports in the same workspace, with matching field names and data types.

Navigation, URLs and hover

Go to Sheet becomes a button with a page navigation action, which is more explicit than Tableau's version: the target is chosen per button rather than derived from a selection. Go to URL becomes a Web URL action on a button, or a column formatted as a web URL when the link belongs to each row of a table.

Actions that ran on hover are a different feature entirely. Power BI's report page tooltips let a whole page act as the tooltip for a visual, filtered to whatever the user is hovering over. That is often a better result than the Tableau original, because the tooltip page is designed rather than assembled from a mark's fields.

The two that do not convert

Change Parameter and Change Set Values both write a value back from a user selection, and Power BI has nothing that does that. Parameter actions are approximated with field parameters, bookmarks, or a disconnected table read back in a measure. Set actions are rebuilt from cross-filtering, drillthrough or bookmarks, depending on which behaviour the dashboard actually relied on.

Neither substitution is a translation, and both are worth pricing separately during scoping. A dashboard with a dozen filter actions is routine. A dashboard whose interactivity rests on parameter and set actions is a redesign wearing a conversion's clothes.

What Antares does with actions

Actions are part of the dashboard layer, so they are inside the conversion's scope rather than beside it. What the Analyzer contributes is the split above, taken before anyone opens a workbook: how many actions there are, of which kinds, and therefore how much of a dashboard's behaviour has a direct target in Power BI and how much has to be designed.

Where the mapping is unambiguous it is converted, and where it is not it is flagged rather than guessed. An action quietly reproduced as the nearest available behaviour is the kind of change that passes review and surprises users in week two. Run the free Analyzer to see the action inventory for your own workbooks.

Related reading: parameters to Power BI and workbook to PBIX conversion. Primary sources: Tableau's actions documentation and Microsoft's guides to buttons and report page tooltips.

← Back to Complete Migration Guide

Related Migration Resources

Frequently asked questions

What is the Power BI equivalent of a Tableau filter action?

Cross-filtering, which is already on by default between visuals on a page, or a drillthrough page when the action opened a separate sheet showing detail for one item. Use Edit interactions to set filter, highlight or none for each pair of visuals.

Why do Power BI visuals filter each other without any action defined?

Because that is the default. Visuals on a report page cross-filter and cross-highlight the others out of the box, which is the reverse of Tableau, where nothing happens until an action is created. Converting a Tableau dashboard therefore includes switching off interactions nobody asked for.

Can every Tableau highlight action be reproduced?

No. Line charts, scatter charts and maps can only be cross-filtered, never cross-highlighted. A highlight action targeting one of those becomes a filter, and the difference is worth explaining to users rather than working around.

Which Tableau actions have no Power BI equivalent?

Change Parameter and Change Set Values, because nothing in Power BI writes a value back from a user selection. They are approximated with field parameters, bookmarks, drillthrough, or a disconnected table read back in a measure. Both are design work and should be scoped separately.

Let's talk migration.

Get your free Migration Readiness Score, or talk to our team about end-to-end delivery.