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

SandDance visual behaves as a slicer + SortByAnotherColumn setting is not taken into account #277

Open
SergiyVV opened this issue Sep 25, 2020 · 0 comments

Comments

@SergiyVV
Copy link

@SergiyVV SergiyVV commented Sep 25, 2020

@danmarshall

There is another issue.
It appears that SandDance visual behaves as a slicer. Is it by design? I doubt it.

What I bumped into is the following.

On a report page there are SandDance visual and a table. The table displays many rows.
I select an item on SandDance visual. This causes the adjoining table to filter and show a record related to the selected item. OK. The data counter of SandDance visual shows "SELECTED: 1". So far, so good.
Then I activate another page of the report. Then I return back to the page with my SandDance visual.
What I see now is that the data counter of SandDance visual shows "SELECTED: 0" and data of SandDance visual indeed looks as if there is no selection/filtering, but the adjoining table still displays only one record as if crossfiltering is still applied.

More over, when I hide SandDance visual, the table still displays only one record as if crossfiltering is still applied. And nothing can be done to get rid of no more welcome filter.
To cap it all, I save the file, close it, then open again and I see the same table with one record only.
The only way to get things normal is to unhide SandDance visual and click on data items, which does the magic - filter will be gone.
The same sample is at your disposal:
InteractionTest.pbix

@danmarshall,
as I mentioned here ##275 (comment), SortByAnotherColumn setting is not taken into account by SandDance visual, which is very frustrating. What do you suggest doing: report it as another issue or my mentioning it will suffice?

It would also be great if selection more than one item using CTRL was possible.
Drillthrough functionality would also be a great contribution.

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

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.