Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Ragged hierarchy Hide Members (Empty) not functioning as expected with multi select on different levels #105

Open
melbark opened this issue Nov 5, 2019 · 2 comments
Assignees
Labels

Comments

@melbark
Copy link

melbark commented Nov 5, 2019

Describe the bug
When Hide Members is set to "Empty" I am unable to make multiple selections within different branches and levels. Behavior is as expected when Hide Member is set to "Never".
Previous versions with Empty Leaves set to "On" also worked as expected.

Something has changed in latest releases and I am unable to roll back to a previous version of the visual as info always shows appsource latest version. Not sure why import from file is not working.
When was 2.0.22 released? I can't see that version in release history.

To Reproduce
Steps to reproduce the behavior:
Crete a multi-level ragged hierarchy and turn Hide Members to "Empty".
for screenshots -> https://1drv.ms/w/s!AhAy9hQRIpG4yzOwS8yexC4hGwus?e=V8YhbY
for example workbook ->hierarchy slicer pattern not working with 2.0.22.zip

Expected behavior
Filter context from leaves at different levels should be passed.

Power BI info (please complete the following information):

  • Online [yes/no]: Yes
  • Browser [e.g. chrome, safari]: All
  • Desktop version: October
@melbark melbark added the bug label Nov 5, 2019
@melbark melbark changed the title [BUG] Ragged hierarchy Empty Leaves not functioning as expected with multi select on different levels [BUG] Ragged hierarchy Hide Members (Empty) not functioning as expected with multi select on different levels Nov 5, 2019
@liprec
Copy link
Owner

liprec commented Nov 6, 2019

Thanks for reporting this and indeed it is a bug. Currently need to validate the last part, write the test case for it and after that I will send a fix for review.

-JP

liprec added a commit that referenced this issue Nov 6, 2019
liprec added a commit that referenced this issue Nov 6, 2019
@melbark
Copy link
Author

melbark commented Nov 6, 2019

Excellent, Thank you for your time and effort.

Outside the scope of this bug but what is the process to build the visual?

npm install
npm run package

results in

  TS2322: Type '(options: VisualConstructorOptions) => HierarchySlicer | undefined' is not assignable to type '(options?: VisualConstructorOptions | undefined) => IVisual'.

Type 'HierarchySlicer | undefined' is not assignable to type 'IVisual'.
Type 'undefined' is not assignable to type 'IVisual'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants