How To Get A Hierarchical Slicer In Power BI

How to Get a Hierarchical Slicer in Power BI

Power BI does not include a hierarchical slicer as a native visual. You add one through the AppSource custom visual library — the "Hierarchy Slicer" by Microsoft — or by using a field well with multiple fields stacked in a standard slicer. This guide shows both methods with step-by-step setup.

Key facts

• The native Power BI slicer supports hierarchy when you add multiple fields in order (Region → Country → City).
• The AppSource "Hierarchy Slicer" (by Microsoft) adds expand/collapse and member count options not available natively.
• Hierarchical slicers work on parent-child relationships in your data model — not on flat lists.
• Cross-filtering works between hierarchical slicers and other visuals on the same report page.
• EPC Group: 29 years of Microsoft consulting. Authors of a bestselling Microsoft Press Power BI book. 10,000+ enterprise deployments.

Method 1 — Native slicer with multiple fields

The simplest approach uses the built-in Power BI slicer visual with multiple fields stacked in order.

1. In Power BI Desktop, add a Slicer visual to your report canvas.
2. In the Field well, drag the top-level hierarchy field first (e.g., Region).
3. Drag the next-level field below it (e.g., Country), then the lowest level (e.g., City).
4. The slicer now shows a collapse/expand tree when you click an item.
5. In the visual Format pane, set the slicer style to List for the hierarchy tree view.

This method has no external dependencies and works in all Power BI Service tenants. Limitations: no member counts, no custom icons, basic expand/collapse only.

Method 2 — AppSource Hierarchy Slicer

The AppSource custom visual provides more formatting options and a richer hierarchy experience.

Add the visual from AppSource

1. In Power BI Desktop, go to the Visualizations pane and click the three-dot menu (…).
2. Select Get more visuals. The AppSource marketplace opens.
3. Search for "Hierarchy Slicer" (publisher: Microsoft).
4. Click Add. The visual appears in your Visualizations pane.

Configure the Hierarchy Slicer

1. Add the Hierarchy Slicer visual to your report page.
2. In the Fields well, drag your hierarchy levels in order from top (Region) to bottom (City).
3. In the Format pane, configure display options: member counts, expand/collapse icons, selection behavior.
4. Set Single select or Multi select depending on your filter requirement.
5. Test cross-filtering with other visuals on the page.

Parent-child hierarchies with PATH functions

When your data model uses a parent-child table (e.g., org charts or account hierarchies), use DAX PATH functions to flatten the hierarchy before adding it to a slicer.

FullPath = PATH(Accounts[AccountID], Accounts[ParentID])
Level1 = PATHITEM(Accounts[FullPath], 1)
Level2 = PATHITEM(Accounts[FullPath], 2)
Level3 = PATHITEM(Accounts[FullPath], 3)

Create calculated columns for each level. Then add those columns to the slicer field well in order.

Use cases across industries

• Healthcare — Region → Hospital → Department → Unit for patient analytics by care location.
• Financial services — Division → Business Unit → Cost Center for P&L filtering.
• Retail — Country → State → City → Store for geographic sales analysis.
• Manufacturing — Plant → Line → Machine for OEE and downtime filtering.
• Government — Agency → Program → Project for budget and spend drill-down.

Best practices

• Define hierarchy in the model — create a formal hierarchy in the Model view rather than dragging ad-hoc fields. This makes the hierarchy reusable across visuals.
• Limit depth to 3–4 levels — deeper hierarchies confuse end users. Flatten rarely used levels into a separate filter visual.
• Test in Power BI Service — AppSource custom visuals must be allowed by your tenant admin. Check org visual settings before deploying.
• Version management — custom visuals update independently of Power BI Desktop. Monitor AppSource for updates and test before applying to production reports.
• Performance — hierarchical slicers with 10,000+ items can slow rendering. Pre-aggregate to the correct grain in your data model.

Frequently asked questions

Is the Hierarchy Slicer a Microsoft-supported visual?

The Hierarchy Slicer in AppSource is published by Microsoft. However, it receives updates separately from the Power BI release cycle. Test each update before pushing to production reports.

Can I use a hierarchical slicer with DirectQuery?

Yes. The slicer works in DirectQuery and Direct Lake modes. However, cross-filtering a hierarchy slicer generates multiple DAX queries. Test performance with your data source before deploying to end users.

Why is my hierarchy slicer not showing child items?

The most common cause is a missing relationship between your hierarchy levels in the data model. Check that each level has a defined relationship and that blank rows are handled correctly. Also verify the field well order — parent must be above child.

Can I sync hierarchical slicers across report pages?

Yes. Use the Sync Slicers pane (View → Sync Slicers) to sync the Hierarchy Slicer across multiple pages. All synced slicers update simultaneously when a user makes a selection.

What is the difference between a hierarchy and a drill-down in Power BI?

A hierarchy slicer filters other visuals based on a selected level. Drill-down changes the grain of a single visual (e.g., from year to month in a bar chart) without affecting other visuals. Both use the same hierarchy definition in the data model.

Talk to a Power BI architect

EPC Group has implemented hierarchical slicers and advanced analytics for Fortune 500 organizations across healthcare, financial services, and government. Call (888) 381-9725 or request a 30-minute discovery call.