How to Connect Two Slicers in Power BI

Cody Schneider••8 min read

Nothing improves a Power BI report like well-designed slicers that let users effortlessly filter and explore data. When one slicer's choice intelligently narrows down the options in another, you've created an intuitive, dynamic experience. This article walks you through exactly how to connect two slicers in Power BI, so they work together seamlessly.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

We'll cover the most straightforward method using your data model and touch on a more advanced approach for when you need extra control over how your slicers behave.

Why Connect Slicers in Power BI?

Connecting, or "cascading," slicers makes your reports much cleaner and easier to navigate. Instead of overwhelming users with a long list of options, you guide them through the data logically. When a user makes a selection in the first slicer, the second slicer automatically updates to show only relevant choices.

Imagine you have a sales report with two slicers: one for "Product Category" and another for "Product Sub-Category." Without connecting them, a user could select "Clothing" from the first slicer, but the second slicer would still list every single sub-category, including irrelevant ones like "Laptops" and "Monitors." This is confusing and inefficient.

By connecting them, when a user clicks "Clothing," the sub-category slicer instantly filters to show only "Shirts," "Pants," and "Jackets." This is the kind of thoughtful design that turns a static report into a powerful, interactive dashboard.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Understanding the Data Model: The Key to Connecting Slicers

Before you add a single slicer to your canvas, the real work happens in Power BI's "Model" view. Slicers don't magically know how they relate to each other, they rely on the relationships you've defined between your data tables. If your tables aren't connected properly, your slicers will always act independently.

The foundation of a good Power BI report is a well-structured data model. Ideally, your data is organized into dimension tables and fact tables (a "star schema," if you're familiar with the term).

  • Dimension Tables: These describe your business entities - the "who, what, where, and when." Examples include a Customers table, a Products table, or a Calendar table.
  • Fact Tables: These contain the events or transactions you want to measure, like Sales, Website Sessions, or Ad Clicks.

Filters applied to a slicer (which is based on a column in a dimension table) travel along these relationships to filter your fact tables, and can also filter other dimension tables. This is how selecting a "Category" in one slicer can influence the available "Sub-Categories" in another.

Method 1: Using Table Relationships (The Standard Approach)

This is the most common and effective way to connect slicers. It's clean, efficient, and relies on having a proper data model. If your data allows for it, this should always be your go-to method.

Let's walk through the product category and sub-category example from start to finish.

Step 1: Get Your Data Ready

First, make sure your data is structured correctly. You need a table that contains both the primary category and a secondary, related category. In our example, we'll assume we have a single Products table that looks something like this:

  • ProductID
  • ProductName
  • ProductCategory
  • ProductSubCategory
  • Price

Alternatively, you could have a ProductCategories table and a ProductSubCategories table that have a relationship between them. For this example, we’ll assume everything is in one clean Products dimension table that has a relationship connected to a Sales fact table.

Step 2: Check Your Relationships in the Model View

Now, let's confirm the connections in Power BI's backend.

  1. On the left-hand toolbar in Power BI Desktop, click on the Model view icon. It looks like three connected boxes.
  2. Find your Products table and your Sales table.
  3. You should see a line connecting them, typically from Products[ProductID] to Sales[ProductID]. This is your relationship.
  4. If you hover over the line, it will highlight the columns being used. If no relationship exists, you can create one by clicking and dragging the ProductID column from the Products table onto the ProductID column in the Sales table.

This connection is what allows selections on product attributes (like category) to flow through and filter your sales data and, by extension, other related fields.

Step 3: Create Your Slicers on the Report Canvas

With the relationship confirmed, it's time to build the visuals.

  1. Switch back to the Report view (the bar chart icon in the left-hand toolbar).
  2. In the Visualizations pane on the right, click the Slicer icon. An empty slicer will appear on your canvas.
  3. With the new slicer selected, go to the Fields pane and drag your main category field (e.g., ProductCategory from the Products table) into the "Field" well of the slicer. You now have your first slicer.
  4. Repeat the process. Add another slicer to the canvas.
  5. With this second slicer selected, drag your ProductSubCategory field (from the Products table) into the "Field" well.

Now you have two slicers on your canvas, one for categories and one for sub-categories.

GraphedGraphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Watch Graphed demo video

Step 4: See Them in Action

Test it out. Click on a category in the first slicer, like "Bikes." You should immediately see the list in the second slicer filter down to only show sub-categories related to bikes, such as "Mountain Bikes," "Road Bikes," and "Touring Bikes."

This works because when you selected "Bikes," Power BI filtered the entire Products table to only include rows where the category is "Bikes." Because the ProductSubCategory column is in that same table, the second slicer's list is automatically constrained to the available values after that filter is applied.

Fine-Tuning Slicer Interactions

Getting slicers connected is a great first step, but a little fine-tuning can make the user experience even better.

The Problem: Seeing "(Blank)" Values

Sometimes, especially with complex data, a child slicer might show a "(Blank)" option. This usually means there are rows in your data where the main category has a value but the sub-category field is empty. It's often not a useful option for the end-user.

Here’s how to hide it:

  1. Select the sub-category slicer (the one showing "(Blank)").
  2. In the Filters pane, find the card for your sub-category field. If the pane isn't open, go to the View tab and check the Filters box.
  3. Expand the card for your slicer field. Under "Filter type," choose Advanced filtering.
  4. Under "Show items when the value," select is not blank from the dropdown menu.
  5. Click Apply filter. The "(Blank)" option will disappear from your slicer.

Method 2: Using DAX Measures for Complex Scenarios

Standard relationships work beautifully in 80% of situations. But what if you need more dynamic control? For example, you only want to show sub-categories in the second slicer if they account for more than 5% of total sales within the selected category. A simple table relationship can’t handle that logic.

This is where Data Analysis Expressions (DAX) comes in. You can write a measure to define exactly which values should appear in your second slicer.

Step 1: The Concept

The strategy is to create a DAX measure that acts like a flag. This measure will return a value (like 1) for every sub-category that meets your criteria, and it will return BLANK() for those that don't. We will then apply this measure as a visual-level filter on our second slicer, instructing it to only show items where our measure returns a 1.

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Step 2: Create a Control Measure

Let's create a DAX measure that will determine whether a sub-category should be visible in our slicer. In this case, we'll only show sub-categories that have actually registered a sale. This is a common requirement to keep slicer lists clean and relevant.

  1. In the Home ribbon, click New Measure.
  2. Enter the following DAX formula in the formula bar:
Is SubCategory With Sales = 
IF(
    COUNTROWS('Sales') > 0, 
    1, 
    BLANK()
)
  1. Press Enter to save the measure.

This measure is very simple. It checks if the Sales table has any rows in the current filter context (i.e., for a given slicer item). If it does, it returns 1. If not, it returns a blank value.

Step 3: Apply the Measure as a Filter

Now, let’s use that measure to control the sub-category slicer.

  1. Select your ProductSubCategory slicer on the canvas.
  2. In the Filters pane, drag your new [Is SubCategory With Sales] measure from the Fields pane into the "Filters on this visual" section.
  3. A filter card for the measure will appear. Under "Show items when the value," select is and type 1 in the box.
  4. Click Apply filter.

Your slicer will now dynamically update. It will only ever display sub-categories that have associated sales data, effectively hiding any that are irrelevant or have never been sold. This approach gives you custom, business-logic-driven control far beyond what standard slicer settings offer.

Final Thoughts

Connecting slicers is a fundamental skill for building clean, user-friendly Power BI reports. The most reliable method is to build on a solid data model with clear relationships, allowing slicers to filter each other naturally. For more complex business rules, using a DAX measure as a filter gives you limitless control over what your users see.

We understand that building interactive dashboards and wrestling with data models can be a steep learning curve that takes time away from acting on insights. Instead of mastering every nuance of Power BI or DAX, you can simply ask for the report you need in plain English. With Graphed, we connect directly to your data sources like Shopify, Google Ads, and Salesforce so you can build real-time dashboards by describing what you want. The complexity is handled for you, delivering the answers you need in seconds, not hours.

Related Articles