Cascading slicer doesn’t refresh immediately when parent slicer changes -parameterised SQL functions

[Nahal_Rasti]

Hi community,

I have two slicers that must cascade:

• AGT (Account Group Type)
• ViewBy

There is a one‑to‑many relationship from AGT[Title] → ViewByAllowed[AccountGroupTypeTitle]. Both slicers can be present in Import or DirectQuery mode depending on the report page; they’re intended to drive SQL functions (via parameters) that shape the downstream result set.

Expected behaviour

• When AGT = Item1 or Item2, ViewBy should show:
• All
• By Agency Profile
• For any other AGT value, ViewBy should show only:
• All

Actual behaviour

1. Select Item1 in AGT
2. Select By Agency Profile in ViewBy
3. Change AGT to another value (e.g., AA)

Expected: ViewBy immediately collapses to All
Actual: ViewBy still shows By Agency Profile until I manually open the slicer and reselect All; after that, By Agency Profile disappears as expected.

Data model (simplified)

• AGT (Import; generated via function)
• ReferenceCodeID
• Title
• ViewByAllowed (Created in Power Query)
• AccountGroupTypeTitle
• ViewByLabel
• Relationship (active): AGT[Title] → ViewByAllowed[AccountGroupTypeTitle] (one‑to‑many)

Other visuals and result tables are produced by parameterized SQL functions; final table visuals arrive using DirectQuery. Only AGT and ViewByAllowed are related; all other logic is function‑driven.

Confirmed settings

• Titles match between AGT and ViewByAllowed
• Relationship is active
• Both slicers are single‑select
• Show items with no data = Off (both slicers)
• Edit interactions set correctly

Attempted solution and error

I tested a DAX-based cascading pattern (measure filtered on the ViewBy slicer) using SELECTEDVALUE, TREATAS, and KEEPFILTERS to allow only valid labels per AGT. When applied as a slicer filter, the ViewBy slicer returned:

“Error fetching data for this visual: an incompatible filter is used on a column with a parameter mapping.”

This looks like a conflict with parameter‑mapped columns used by the function that receives the slicer values.

Why this matters (design requirement)

This isn’t a one-off report quirk. We’re building a system where slicers are intentionally used as SQL function parameters. Those functions:

• Accept slicer selections as parameters
• Dynamically generate the result set (including columns)
• Are reused across multiple reports (some datasets use Import, others DirectQuery)

Because of this, we need predictable, immediate cascading behaviour. Relying on users to manually re-select values is not viable.

1. What is the recommended modelling pattern to ensure the child slicer (ViewBy) immediately refreshes when the parent (AGT) changes in a mixed Import + DirectQuery and parameterized function setup?
2. If DAX filtering on the slicer is incompatible due to parameter mapping, is there a supported alternative (e.g., bridge table pattern, disconnected slicers + measures + field parameters, or a different relationship/filtering approach) that preserves immediate cascading without user intervention?

Any official guidance or proven patterns would be greatly appreciated. Thanks!

[anilelmastasi · Accepted solution]

Hello @Nahal_Rasti ,

Could you review this documentation please?
https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-dynamic-m-query-parameters#unsupport...

[Nahal_Rasti]

Thanks for the link, much appreciated. I’ll review the documentation and test this when I get a chance (Friday afternoon here), and will report back with the outcome.

[v-achippa]

Hi @Nahal_Rasti,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @anilelmastasi for the prompt response. 

As we haven’t heard back from you, we wanted to kindly follow up to check if the response provided by the user for the issue worked? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @Nahal_Rasti,

We wanted to kindly follow up to check if the response provided by the user for the issue worked? Did you got any chance to review the documentation? or let us know if you need any further assistance.

Thanks and regards,

Anjan Kumar Chippa

[Nahal_Rasti]

Hi @v-achippa,

Thank you for following up, and many thanks to @anilelmastasi for the very helpful link.

I had a brief sign-in issue due to an email mix-up, but it’s now resolved. I’ve reviewed the documentation and noted the limitations and unsupported items for Dynamic M query parameters.

Appreciate your support.

Kind regards,
Nahal