Hierarchical Slicer Display Issue When Filtered by DAX Measure - Feb 2024 Update

[BIscoverer]

Hello everyone,

I've run into a challenge with hierarchical slicers in Power BI following (I suspect it to be related to February 2024 update) and would greatly appreciate any guidance or insight you might offer.

Issue: After applying a DAX measure as a filter on a hierarchical slicer (countries as parents, cities as children), the slicer started duplicating parent entries corresponding to the number of child items. This results in an abnormal display that complicates user interaction and understanding.

• Expected behavior: Each country appears once, listing its cities underneath.
• Actual behavior: Countries are duplicated based on the number of cities. For instance, "CountryA" appears three times for its three cities.

That's how it looks like:

> CountryA

> CountryA

> CountryA

>> City A.1

>> City A.2

>> City A.3

> CountryB
> CountryB

>> City B1

>> City B2

Quesitons:

1. Is this behavior a known issue with the February 2024 update of Power BI?
2. Are there any recommended workarounds or solutions to correct the slicer display without excluding a filter by the DAX measure?

Many thanks!

[BIscoverer · Accepted solution]

The issue with the hierarchical slicer has resolved itself. It no longer appears in the slicer or matrix visual, and I suspect a recent Power BI update might have fixed it. I didn’t make any changes or apply any workarounds, so it seems to have sorted out on its own.

Thanks to everyone who considered my question. I will mark this as resolved.

[v-xinruzhu-msft]

Hi @BIscoverer 

What is your measre like? It may be affected the measure you have create , can you provide some sample data and the logic of the measure (e.g what is the condidiotn of thes slicer?) so that can provide more suggestion for you.

Best Regards!

Yolo Zhu

[BIscoverer]

Hi @v-xinruzhu-msft,
Thank you for your response!

The issue I mentioned occurs regardless of the specific measure applied as a filter on the slicer. However, to give you a concrete example, here is one of the measures I've experimented with:

Measure =
VAR _var1 =
IF(
    ISBLANK('Table1'[Amount1]),
    BLANK(),
    0
     )
RETURN
IF(
    VALUES('Switch'[Switch Yes No]) = "Yes",
    [Amount2] + _var1,
    [Amount3] + _var1
    )

The filter on the slicer is based on whether this measure is not blank.

The fields used in the slicer (Country and City) are from the same table.

Regardless of the measure used, if it's applied as a filter to a hierarchical slicer, the parent level (in this case, Countries) duplicates based on the number of child items (Cities). This duplication does not seem to depend on the specific logic of the measure but rather on the presence of any measure applied as a filter.

The only workaround I found so far is using a third-party slicer from AppSource (e.g. HierarchySlicer). Then the duplication problem does not occur. Yet, I would really like to use the native Power BI slicers.

I would be grateful to hear any suggestions or insights you might have on addressing this issue.

[v-xinruzhu-msft]

Hi @BIscoverer 

Please check your relationship among your table, are the fields of the measure same as the field you put into the slicer? After testing, the slicer can work well in my report.

Best Regards!

Yolo Zhu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[BIscoverer]

Hi @v-xinruzhu-msft ,

Thanks for your advice and testing this on your end.

This setup previously worked without any issues (before February 2024 update), so the relationships and field alignments should be correct.

I suspect the issue might be due to my measure referencing another measures ([Amount1], [Amount2], adnd [Amount3] are the measures, one of which is report-stored one).

Could the update have introduced changes affecting slicers with measure-based filters, especially those referencing other measures?