Click on SEVERAL visuals to slice
What is really missing in Interactions is one simple feature:
The ability to click on SEVERAL visuals to slice the report. Currently the users only can click one. The click on another visual "removes" previous selection, so the users loose their "data exploration thought flow"...
For instance, I have two bar charts (Product and Country) and one table. I would like to click on "Bicycles", then click on "USA" so the table shows only sales of Bicycles in USA.
Currently, when I click "USA", my previous "Bicycles" selection is removed.
Please add this option to keep all the selections from different visuals.
Missing this feature for ages! Why does it take so much time to add it, all the functionality is already developed :(
Dear Power BI development team, please, don't "deselect" whatever is selected in a visual when I click another visual (if [Shift] key is pressed or some screen key for touch users)
This is a basic foundation of every (?) other visual BI tool (Qlik, Tableau, Lumira etc.) It has been requested on so many places now but with very little response from the PBI team. The filter visual does exactly this, why cannot the charts and tables work the same way?
Mike Lees commented
Just found a "slicer" visualisation tool in PowerBI desktop (not checked online version to see if it's there too). It does what it says on the tin! I have used multiple slicer tools on the same page, linked to different data fields and they produce multiple, stacked slices of the data.
Using the tool when a field linked to the tool is already in another visual is a little wasteful of page real estate, but it's a small price to pay for this functionality.
Well done DevOps team for listening to your customers and thank you!
Mike Lees commented
I believe that it is possible to slice a report using up to three concurrent filters, but only using the "Visualisations" control in the desktop. The filters have "visual", "page" and "report" scope. It appears to me that this was the original intention, but that requests for "point and click" functionality caused the "visual" filter to be extended to accept a "point and click" event (fair enough) *and* extended to have "page" scope", which then causes logical hierarchy decision problems if this is extended to multiple clicks.
Reason why I believe this is true. I experimented and found this behaviour: Create a report with multiple visuals, visualising the same data. Make one of them multiple level. Make a selection in a single level visual. Check that the visual in the multiple level visual changes (your data views intersect). Now go down one level in the multi-level visual. Click in an element of the visual. That visual changes but the single level visual doesn't. Now go up one level. The view at this level has changed (assuming that this view would change with the selection just made at the previous level).
Implementation suggestion: Users need to make a functionality choice and know that they have done so and how to reverse out if it was a mistake or if they get "buried". So implement a high level filter functionality selection menu with filter scope selections: Single slice page only; Multi slice page only; multi slice all report; Reset filters. Breadcrumbs would be good to follow selection history. If the user could select any breadcrumb to get to that filter point then a "reset" option isn't needed in the menu.
I totally concur. This is essential when we need to carry out investigative analysis. We investigate accidents which occur on merchant ships for our principals. We have tons of data which can help us identify patterns. I don't want to use too many visual as we prefer data in tables. The thing about tables is that data is filtered as per the row we select but as soon as data from the other table is selected, we ten to loose our previous selections, which to say the least is very annoying. Is there a way to lock the filters
I also totally agree. I would be great to have an option on the "nothing" icon in "edit interactions" to avoid the selection on the visual to be removed when another selection is made on another visual. It would really improve data exploration with a better user experience.
Mike Foss commented
Totally agree this would be a great improvement. depending on the visual they will unfilter when interacted with. It would be nice not to have to add filters on the report and instead trust that slicers would apply each filter based on what visual is clicked on. Sure this works if you build a slicer with the hierarchy you want and drill down but sometimes you just do not want to drill down.
If I understand your concern, it is possible. Currently I have a dashboard I'm creating with one slicer with years and a second slicer with County. In order for it to work, I had to add a column in my excel file and duplicate the years going down. I hope that helps.
Doesn't this work if you have a proper hierarchy? At least this works for me on a date hierarchy. Put Years in one slicer, Months - in another and here you go.
@Adam Ctrl click only filters multiples within the same visual (for me anyway). What is being asked is the ability to click within multiple visuals and each retain the filtering of what was selected. I'm desperate for this feature too. Right now I have to add many slicers to reports to achieve this and it really detracts from the data exploration process.
Not sure if I am barking up the wrong tree here, but I just hold Ctrl and that lets me click on multiple visuals at once
This would be awesome!
John Fitzpatrick commented
Same idea has been posted multiple times. Please upvote on this one as it has the most votes and has gained MS attention.
Rafael Baleche commented
I build a report that uses several visuals as filters, but when I select a value from a visual, automatically the other selections in other visuals are cleared and it is not possible to complete the analysis, being necessary to include slicers on the canvas, reducing the space available for other visuals.
Yes, this really needed. And this I something that makes it difficult moving from QlikView/QlikSense as the users are used to this feature. Once you have it, you can live without it.