[BUG] Sync only partially working under some circumstances

[Aexalon]

We've run into a issue with syncing HierarchySlicers, in that under certain circumstances, two identical synced HierarchySlicers on two different tabs of a report still seem to completely lose visualization of the internal filter state when switching between those tabs.

Steps to reproduce the behavior
In Hierarchy slicer bug demo.zip:

1. Start in tab "Test1", and clear the HierarchySlicer by selecting and then unselecting "Select All"
2. Select the entries "fou_sXFjT9v/", "rev_dp2tCsEg" and "col_D6Cky1L+"
3. Switch to tab "Test2"
4. The HierarchySlicer there will show no selected entries, while the other visuals on the tab clearly still reflect the inner filter of the HierarchySlicer.

Expected behavior

• The HierarchySlicer in the second tab still show the selected entries.

Power BI info (please complete the following information):

• Desktop version: Version: 2.88.1385.0 64-bit (December 2020)

[liprec]

Thanks for the feedback and looking into the issue I can confirm that it is a bug regarding the sync option in combination with the blanks/null in the ragged hierarchy. TL;DR: Some code is exiting to early because the value is null.

The next version will contain a fix for this issue, but unfortunately it will take some weeks before it is available to everybody.
A possible workaround is to alter the source to replace the nulls in the hierarchy with the parent name and use that option to hide the not needed levels.

[Aexalon]

Thanks you for providing a workaround, which we've successfully tested.

Kudos for identifying the problem so quickly; we look forward to your next release.

[DrPepperShaker-CA]

Hi @liprec. This is an older bug which, from the notes above, should be resolved. However, I am seeing this issue (sync between pages not working) in version 2.2.2 of the app. The issue shows up when:

1. Select a parent node using Click. All child nodes in that branch are automatically selected.
2. Ctrl+Click to deselect some child nodes.

Is this a separate issue from what was reported in this bug? Thanks.