Tableau Groups and Hierarchies to Power BI: Groups, Bins, and Mapping Tables

Tableau groups combine dimension members, either to fix data errors, such as merging "CA" and "California", or to roll members up into a coarser category. Power BI has a feature with the same name and the same right-click gesture, so the conversion looks trivial. It usually should not be done that way. A Tableau group carries business meaning that deserves to live in the model as a column, not as a report-level convenience nobody can find later.

Grouping options in Power BI

Four ways to group, and which one survives contact with a migration

Power BI grouping is created by selecting elements in a visual and choosing Group, or by right-clicking a field and choosing New group. The result is a new field with (groups) appended, and members can be edited later in the Groups dialog, including moving leftovers into an Other group. For a small, report-specific grouping this is exactly right, and it is genuinely the closest match to the Tableau gesture.

It ages badly at scale. The membership list lives in the model's metadata, it is edited through a dialog, and nobody reviewing a change can see what moved. A calculated column with SWITCH states the rule in one readable expression. A conditional column in Power Query pushes the work upstream, keeps the model smaller, and can fold to the source. And when the grouping is a business mapping rather than a convenience, the honest answer is a mapping table loaded as a real dimension, joined on the key, and maintained by whoever owns the definition.

Use the Tableau group's size as the signal. Three members merged to fix a typo is a group. Two hundred products rolled into fifteen reporting categories is a dimension table that was living in a workbook because Tableau made that the easy option.

One clarification saves a recurring argument during migration. A group merges members into a coarser category and behaves like a column. A set answers a yes-or-no membership question and can be dynamic. A hierarchy defines a drill path between levels that already exist. Tableau users often reach for a group where the requirement is really a set, or the reverse, and the Power BI targets are genuinely different: a column, a filter expression, and a model hierarchy. Sort that out before writing anything.

Binning

Tableau bins and Power BI bins line up closely. Right-click a field, choose New group and set a bin size, and a new field appears with (bins) appended. Two documented constraints matter when planning: bin sizes can be set for numerical and time fields, and you can create bins for calculated columns but not for measures. A Tableau bin built on an aggregate therefore needs the underlying value materialised as a column first, which is a modelling step rather than a formatting one.

Hierarchies

A Tableau hierarchy adds the plus and minus controls on a shelf. A Power BI hierarchy is created in the model by dragging fields together, and users move through it with drill mode in the visual rather than by expanding the axis. The behaviour differs in one way worth explaining to users before go-live: by default, drilling one visual does not affect the others on the page, though you can set drill-down filters to apply to the entire page.

Watch date fields in particular. If auto date/time is enabled, Power BI builds a hidden date table for every date column, which inflates the model and interacts awkwardly with field parameters. Most estates are better served by one proper date table with an explicit hierarchy, defined once in the model.

What Antares does with groups and hierarchies

Groups and hierarchies are inventoried with the rest of a workbook's structure, and the count is what makes the decision above cheap to take: a workbook with two typo-fixing groups and one with a two-hundred-member category mapping look identical in a feature list and are completely different pieces of work.

Where a group is a straightforward member list, conversion handles it. Where it encodes a business mapping that ought to become a dimension, that is a modelling decision for the team that owns the definition, and it is flagged rather than guessed. Run the free Analyzer to see the breakdown for your own workbooks.

Related reading: sets to DAX and calculated fields to DAX. Primary sources: Tableau's grouping documentation and hierarchies guide, plus Microsoft's SWITCH function reference and star schema guidance.