microsoft / microsoft/SandDance

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

Open
#277 1 comment 0 reactions 1 assignee View on GitHub

@danmarshall is already working on this.

Since Jan 13, 2023.

bug
Dominant language
TypeScript
Stars
7.1k
Forks
573
Avg merge
8d 9h
Merged PRs (30d)
4

Description

@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 #https://github.com/microsoft/SandDance/issues/275#issuecomment-698833512, 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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.