Forum Discussion
drill down based on legends
To achieve this you need to use the 3rd button from left to right in the Top left corner of the visual
The Expand all down one level in the hierarchy button
then the axis will display all
Good Luck! :smileyhappy:
"Expand all one level down in the hierachcy" is working file, but it has several item on the x-axis, Month-ProductName (eg: Jan-ProductName1, Jan-ProductName2... Feb-ProductName1, Feb-ProductName2.. and so on).
I need just Jan, Feb, March on x-axis and Porduct details "drilling down" and stacked area chart like below
- Anonymous8 years agoNot applicable
Did you ever get a resolution on this, I would like to accomplish the same task.
- Quentin5 years agoHelper IV
Any update on this? is the issue with the calculated table the solution?
- DouweMeer7 years agoImpactful Individual
No one gets it :).
I created for this a second custom table with an unpivot on those 4 columns and a relationship with the ID between them. Then 1 Chiclet slicer for the unpivotted table and 4 'classic slicers'.
But yes, I'm quite curious if there is an easier way for my end users to get a drill down on legend.
- evang5507 years agoMicrosoft Employee
I would love this also, would be very powerful.
- DouweMeer7 years agoImpactful Individual
This is the closest workaround I could do so far (x-axis should be named legend, I know). But still, if you wanted to pin it for just 1 of the types, you have to click an option of a 'normal' slicer and then hit the subtype option. I've created something similar for the y-axis as well so it would be completely flexible.
My problem so far is, it is fancy, but mainly used for data exploring to see how different section are related to each other. This is generally done by those who already know how Power BI works. And as soon as you find the consistency, you pin that consistency against the wall and the dynamic drill down is no longer required.
Perhaps when I get to the sales numbers instead of KPI's, that this might become interesting.
- Anonymous4 years agoNot applicable
I get it. I'm having the exact same issue as a new user of PowerBI and to be honest I thought this would be easy seems like this is what PowerBI is meant to do.