Cascading / Dynamic Filter Response help

[GanesaMoorthyGM]

Hi everyone,

I need help configuring my Power BI slicers so they behave responsively based on user selections.

I have the following filters:

• FiscalYear

• Month

• Country

• Location Code

What I need is cascading behavior. For example:

• If the user selects FiscalYear = FY25, then the Month, Country, and Location Code slicers should only list values that exist within FY25.

• If the user selects Country = US, then the Location Code slicer should only show locations from the US (not all countries).

• Essentially, each slicer should dynamically update based on selections in the other slicers so users only see valid values, not the entire dataset.

I have tried normal slicer interactions, but some values still appear even when they don’t exist in the filtered context.

To be more precise:

Example:
See i select Country "Qatar" so Im expecting it to list only Qatar's Locationcode but here all the LocationCode is appearing.

Does anyone know the correct setup or if there are limitations on cascading slicers?
Any guidance is appreciated. I can share screenshots if needed.

Thanks!

[GanesaMoorthyGM · Accepted solution]

Guys I solved by using a measure like:

Cascading filter = INT ( NOT ISEMPTY(fact_sales))

And add this is in all slicers visual lvl filter for all slicers eg:FiscalYear,Month,Country,Location_Code

Now it is acting fine.

Thank you for your response @v-echaithra , @rohit1991 .

[v-echaithra]

Hi @GanesaMoorthyGM ,

Thank you for providing an update and confirming that the issue has been resolved. If you require any further assistance. Please feel free to let us know, we’re happy to help!

Thank you 
Chaithra E.

[v-echaithra]

Hi @GanesaMoorthyGM ,

To make cascading slicers work in the new Power BI slicer experience, ensure that each slicer field comes from a dimension table with a single-direction relationship into the fact table, and remove any relationships that bypass the fact table. When the fact table becomes the only path between Country, Location, Month, and FiscalYear, Power BI automatically shows only the valid values for the selections.

Open Model view.

Ensure relationships are exactly like this:

DimFiscalYear > Fact

DimMonth > Fact

DimCountry > Fact

DimLocation > Fact

Make sure Relationship direction = single (one-way), no bidirectional filters, no direct relationship between DimCountry and DimLocation. Also verify the fact table contains the Country + Location combinations that you expect.

Hope this helps.
Thank you.

[rohit1991]

Hii @GanesaMoorthyGM 

Power BI slicers do not automatically cascade unless the data model supports it.
To make Country >> LocationCode responsive, ensure they come from separate dimension tables and correct single-direction relationships exist.
Use DimCountry and DimLocation tables in slicers  not fields from the fact table.
Once the model is corrected, selecting “Qatar” will only show Qatar’s LocationCodes.

[GanesaMoorthyGM]

Exactly all my Slicers are from Separate Dim tables @rohit1991 .