Why is Filter Not Working in Power BI?

It’s one of the most frustrating moments for any Power BI user: you set up a slicer or a filter, click on a value, and absolutely nothing happens. You’re left staring at your dashboard, wondering why your perfectly good filter is suddenly broken. This article will walk you through the most common reasons why filters fail in Power BI and provide clear, step-by-step solutions to fix them.

Graphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Build Your First Dashboard

Finding the Source of the Problem

When a Power BI filter isn't working, the problem almost always falls into one of three categories: a broken data model relationship, a misconfigured visual or slicer setting, or a DAX measure that is intentionally ignoring the filter context. We’ll look at how to diagnose and solve each of these issues methodically.

Step 1: Start with the Filter Itself

Before diving into the complexities of your data model, check the most obvious culprit: the filter itself. In the Filters pane, Power BI has three levels of filtering, and a setting in one can easily override another:

• Filters on this visual: Only applies to the specific chart or table you have selected.
• Filters on this page: Applies to every visual on the current report page.
• Filters on all pages: Applies globally across your entire report.

A "broken" slicer on your page is often just being overruled by a contradicting filter hidden in the "Filters on all pages" section. Expand each of these sections in your Filters pane to make sure there isn't an unexpected filter locking your data in place.

Step 2: Check Your Visual Interactions

Sometimes a filter is working, just not on the visual you're looking at. Power BI allows you to control how visuals on a page interact with each other. It’s possible that the interaction between your slicer and a specific chart has been turned off.

To check this:

1. Click on the slicer or visual that’s supposed to be doing the filtering.
2. Go to the Format tab in the ribbon.
3. Click on Edit interactions.

You’ll see small icons appear on the other visuals on your page. Each visual will have a filter icon and a "none" icon (a circle with a line through it). If the "none" icon is selected for a particular chart, that chart will ignore any selections made in your slicer. Simply click the filter icon to re-enable the interaction.

AI for Data Analysis

Crash Course

Graphed

Free PDF Guide

AI for Data Analysis Crash Course

Learn how to get AI to do data analysis for you — the best tools, prompts, and workflows to go from raw data to insights without writing a single line of code.

Download Free Guide

Diving Deeper: Bad Relationships Spoil Good Filters

If your quick checks on the report canvas didn't solve the problem, the issue is likely hiding in your data model. The quality of your filters depends entirely on the quality of the relationships between your data tables. A misconfigured relationship is the number one cause of filtering headaches.

Navigate to the Model View

Click on the Model view icon on the left side of the Power BI interface to see how your tables are connected. The lines connecting your tables represent the relationships. Hovering over a line will show you which columns are linked. Here’s what to look for.

Problem 1: Incorrect Cross-Filter Direction

The direction of a relationship determines how filters flow between tables. You can see arrows on the relationship lines that indicate this flow.

• Single Direction: This is the default. If you have a Products table and a Sales table, a single-direction filter allows you to filter your sales data by selecting a product. However, it does not let you filter your products by selecting something from the sales table. For example, selecting "high-value sales" in your Sales table won’t automatically update a slicer to show only the products involved in those sales.
• Both Directions: This allows filters to travel "uphill" or "downhill." In the example above, setting the direction to "Both" would allow you to select a product and see its sales, and to select high-value sales and see which products were sold.

The Fix: Double-click the relationship line to open the settings. Find the "Cross-filter direction" dropdown and change it from 'Single' to 'Both.' Be cautious, however. While enabling "Both" often fixes immediate filtering problems, overusing it in a complex model with many tables can create ambiguous filter paths and negatively impact performance. Use it only when necessary.

Graphed

Your AI Data Analyst to Create Live Dashboards

Connect your data sources and let AI build beautiful, real-time dashboards for you in seconds.

Build Your First Dashboard

Problem 2: The Inactive Relationship

Power BI only allows one active filtering path between two tables at a time. If you have multiple relationships between the same two tables (e.g., your Sales table has a Ship Date and an Order Date, both connecting to your Calendar table), only one can be active. The active relationship is shown as a solid line, while inactive ones are dotted.

If your filter is based on an inactive relationship, it won’t work. For instance, if you’re filtering by Ship Date, but the active relationship is on Order Date, your slicer won't do anything.

The Fix: You have two options. First, you can go into the relationship editor and manually set the desired relationship to "active," but this will deactivate the other one. The more flexible solution is to use the USERELATIONSHIP function in your DAX measures. This function allows you to temporarily activate an inactive relationship just for that one calculation. Here’s an example:

Sales by Ship Date = 
CALCULATE(
    SUM(Sales[SalesAmount]),
    USERELATIONSHIP(Sales[ShipDate], 'Calendar'[Date])
)

This measure will calculate total sales based on the ship date, effectively ignoring the active relationship on order date for this specific calculation.

When Your DAX Measure Is the Rebel

The final place to check is inside your DAX measures. Sometimes you write a DAX formula that is specifically designed to ignore filters, so when you try to apply a slicer to it, nothing happens. It's not broken, it's just following orders.

AI for Data Analysis

Crash Course

Graphed

Free PDF Guide

AI for Data Analysis Crash Course

Learn how to get AI to do data analysis for you — the best tools, prompts, and workflows to go from raw data to insights without writing a single line of code.

Download Free Guide

Watch Out for Filter-Modifying Functions

The CALCULATE function is the engine of DAX, but it can be used with other functions that modify or even remove a report's filter context. The most common culprit is ALL().

Let's say you have this measure:

Total Sales All Regions = 
CALCULATE(
    SUM(Sales[SalesAmount]),
    ALL(Store[Region])
)

The ALL(Store[Region]) part of this formula explicitly tells Power BI to remove any filters applied to the Region column. If you add a "Region" slicer to your report page, its selections will not affect any visual using this measure. This is useful for calculating percentages of total (e.g., what percentage of all sales came from the North region), but it can be confusing if you forget it’s there.

Other functions that can behave similarly include ALLEXCEPT(), REMOVEFILTERS(), and ALLSELECTED().

The Fix: If you need a measure to respond to a slicer, make sure its DAX formula doesn't contain a function that is actively fighting it. Review your measures and remove or adjust any ALL() functions that shouldn't be there. If you inherited the report, you may need to trace the measure's logic to understand why the original author chose to ignore certain filters.

A Quick Checklist for Troubleshooting

Feeling overwhelmed? Don't be. Next time a filter refuses to cooperate, run through this simple checklist:

1. Check the Filter Pane: Look for any sneaky "page-level" or "report-level" filters that might be getting in the way.
2. Edit Interactions: Make sure your slicer is actually connected to the visual you expect it to filter.
3. Review the Model View: Look for issues with cross-filter direction (is it Single instead of Both?) or inactive relationships.
4. Inspect Your DAX: Double-check that your DAX measures aren’t using functions like ALL() to deliberately ignore the filter.

Final Thoughts

Almost every Power BI filter issue can be traced back to the relationship model, visual integrations, or a DAX formula intentionally overriding your selections. By systematically checking these areas, you can quickly diagnose the problem and get your interactive reports working as intended.

Wrestling with cross-filter directions and DAX puzzles is why we built a tool that handles data analysis more intuitively. With Graphed, we connect directly to your various data sources, letting you create dashboards with simple conversational language. This approach lets you spend less time troubleshooting puzzling filter behaviors and more time getting clear, real-time answers from your data.