It has ruined my drill downs as well. Here's the thing - the layering is a beautiful and powerful thing, but dashboard authors often will layer different cuts that aren't necessarily a hierarchy! (Our data is more rich that the standard products hierarchy often used in examples) We definitely need the ability now (not a month from now) to have the in-line hierarchy be an optional thing, as it was when it was a preview feature. Optimally, it would be a visualization to visualiztion option. It's also disappointing that the change was made to reports and dashboards that I didn't even republish since the general availability of the feature went live. Our visuals should not fundamentally change without us taking action.
Couple thoughts and solutions on this topic…
Let me know if this helps!
Alex.
Alex,
Thank you for the suggestion but unfortunetly that doesn't really help I believe.
I've logged this as an issue at the below address and hope we can expedite this as much as possible. Thank for you consideration.
I couldn't agree more with Mike. We should not have to do a workaround that isn't as insightful for something that was already perfect and suited out needs. I too hope that this fix is expedited and the service can be changed back this weekend. I will reiterate that this is a function that users should have control over whether to use or not. I was demonstrating the expand functionality in a presentation yesterday and was railroaded by the un-readability that this unexpected change brought. What should have warrented a "wow" instead wound up with me apologizing for the product.
Hi everyone! Thanks for the feedback. This is very helpful for us! I just want to let everyone know we hear you and are looking into this, both ways to improve the experience and giving y'all finer control over how the feature works.
@zapppsr The fact that you are lossing your legend is a bug, we are looking into it right now and working on a fix.
@Tishchenko, would you mind sending me your pbix file so we can investigate a bit more? You can send it to amac@microsoft.com. If you can't share it with me, could you send me some images that include the fieldwell of the column chart?
Thanks Mike. We understand the issue and looking for options of resolving this quickly. Stay tuned...
Thanks,
Alex.
Hi @Amanda, thanks for replying. It is always good to know there is someone looking our requests.
Regarding my chart, even if in that specific case it is a legend bug, on other charts where dates are not present, the new in-line hierarchy changed the context and even some numbers. Eg.:
If I had in the first level Cities, and on the second level Products, it would be like this:
Data:
City 1 - Product A = 10
City 1 - Product B = 20
City 2 - Product A = 100
City 3 - Product B = 200
Previous Drill Down method and In-line Hierarchy:
Level 1:
City 1 = 30
City 2 = 300
Level 2: - (Expand All Drill Down)
Product A = 110
Product B = 220
Level 2: - (In-Line Hierarchy Drill Down)
City 1 - Product A = 10
City 1 - Product B = 20
City 2 - Product A = 100
City 2 - Product B = 200
You can see, now, I miss some important information which was the sum of products, regardless the previous hierarchy.
As I mentioned before, congratulations, this is a new feature and very welcome, but not as a replacement for the old Expand All Drill down non-hierarchy bound. Specially when that change affect our reports in the middle of a meeting...
They are completely different ways of looking at data. And the old method is somehow more efficient in some scenarios, where I can have multiples charts in one, using the drill down.
I still advise adding a new button on the visuals allowing both drill downs (normal and in-line hierarchy) is the solution to benefit most people.
Do you know if this will be fixed only on next desktop release or will it be patched soon? At least if it is changed on the Power BI Online Service and you could spare us fixing some charts that would be great.
Thank you again for your help and please take our feedback as a means for improving this great tool which is Power BI.
Great Point @zapppsr. The change in the actual numbers is a big impact as well.
Thanks @zapppsr for this great example! We actually used your example in our conversations here. As Alex mentioned, we are looking to release an update for this as soon as possible and are investigating options. You should hear something from us again in the next several days with a better estimate as to when the update will occur.
Hi, @Amanda, can't send my PBIX, but simalar behavior you can investigate on Microsoft Solution Template "Campaign/Brand Management for Twitter" https://powerbi.microsoft.com/en-us/solution-templates/brand-management-twitter/