Forum Discussion
How to disable the automatic inline hierarchy???
Please, make this new (from august update) fiture optional!!! (on/off)
Thanks LanceDelano! Seems, last service build 13.0.1605.489 works exactly as you promised!
But i'm have some question about buttons image quality. (see picture. This screenshot was made from Edge with 200% zoom)
54 Replies
I've added my same issue to the issues forum as I think this is a bug they didn't consider. I've referenced this post as well. Upvote mine to help out please.
Ok, I will. Thank you!
Tishchenko Looks like you've got field on x-axis as type Text otherwise if you drop date field onto x-axis you usually get drill down in form of Year -> Qtr -> Month -> Day. You can disable that feature by going to File -> Options and Settings -> Options -> Data Load and untick time intelligence feature as shown below.
Thank you for your comment. We are immediately working on a button that will preserve the old behavior and new separate button that will enable the new behavior. I can't promise an exact timeline at this point, but we have heard the feedback and consider this a super high priority. So, it will be soon. The new behavior, as a side comment, will improve in readability over time as well.
Hi ankitpatira, this option "Auto Date/Time alredy disabled in my PBIX.
Look at this video, how this new "cool" fiture broke all of my reports
(before this update, drill works ok!)
HI.
I always try to think positively about change. The new in-line hiearchy feature will bring possibilities that we didn't have before, but it is taking away some we already have and like.
I know many workarounds to solve the problem in my chart below, but I dont't have only one like this.
One problem I see is changing the Power BI Online Service in a way that the visuals start presenting different views and numbers is not a good practice. We are caught off guard in the middle of a presentation with numbers we are not expected to see... I mean numbers, because this new in-line hieararchy group information that previously where separated.
When releasing such a feature, I recommend making it in a way that the previous view is kept and we can have the new view if we like. It is not that hard. Imagine, in this case, a new Drill Down button is added that goes in-line hierarchy, but we stil have the expand all button behaving the same way before...
Now I have many charts to adjust to this new way of drill down.
I believe in features that add new options, but do not replace good options broadly used.
Please fix this, adding a new button to opt between normal or in-line drill down.
Ankitpatira, your suggestion does not fix the problem.
:catsad::mansad::robotsad:
resilience required from this .... Not enough to Frown anymore.
who every come up with the automatic inline hierarchy function is a moreon!!!!!!!!!!!!!!
diable it when the next update.
Learn how Tableau to their things ok?
it killed my reports aswell
it killed my reports as well
definitely needs a way to switch off per visual
Before
After
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…
- Consider changing from Column to Line chart. Line chart will use the continuous axis even if you use hierarchies and also now support drill and expand capabilities. Continues axis support for Column chart will be coming soon.
- You can switch from using the Hierarchy to Date Field per visual in the Field list. You can do this by clicking on the chevron next to the date field.
- We are working on improving the labels for categorical hierarchy mode on Column and Line charts. They will be nested without repeating of same text. Expect this soon.
Let me know if this helps!
Alex.
Alex,
Thank you for the suggestion but unfortunetly that doesn't really help I believe.
- This would require changing Multiple reports and training users on new functionallity as well line charts don't always make sense for what we need to convey.
- The problem is associated with more than just date fields. If I have text fields for Distributor, rep and customer I'm not using any hierarchy function. The chart is unreadable when we drill down.
- While I'm sure everyone apprecitate the constant improvments this is a real issue that has rendered many of my current reports and charts unreadable. This shouldn't have been a default update that changed previously built visuals. I really should have been an option for each visual or something of that magnitude.
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 [email protected]. If you can't share it with me, could you send me some images that include the fieldwell of the column chart?
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.
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/
Amanda and LanceDelano,
I've found an additional Issue with this update that is pretty significant. When focusing on a visual that has drill down information, it's not providing the proper filtering to visuals that are linked to it. I know you guys are working on it but it needs to be quick, my teams are losing faith in the product. See below for an example:
I don't see the other issue with this inline hierarhy update described above: The measures used in visual are calculated to the item in the top of the hierarhy despite being drilled down to more detailed view.
Example:
We have a Team and Product Managers in that team. We have "Wow factor" target per product. We create a mesure to calculate the targets:
PM_A: 100 wows
PM_B: 200 wows
Team_A: 300 wows
When I put Team_A above PMs in visual and then drill down, the tooltip shows me that PM_A has a WOW target of 300
It destroys informational value of most of the dashboards we publish to our colleagues
Not exactly sure how you've written your measure. There are lots of ways to author these kinds of measures. However, the point is that a simple aggregate (e.g., SUM, AVG, etc.) with no Calculate or other mucking with the filter context will automatically filter the data to be at the leaf level of the hierarchy. So, say a measure of Average NPS (Net Promoter Score) that is calculated as you go down a hierarchy (Say Region and then Product) will absolutely work correctly. At a leaf level (Say Washington State and then Product A) the data will be filtered to WA and then Product A and the aggregate (Avg) will aggregate over that data. When you move up to just Region you would be able to see the Avg NPS for WA.
All that said, we are finally very very close to publishing an update that will give the old button the old behavior and a separate new button that will enable the new behavior. As Alex mentioned on a different response, there were some issues in terms of how these features worked with other parts of the product that we had to work through. That is all done now and we've begun the update process. Again, I don't want to give a specific day (since delays seem to inevitably happen) but process wise now it's a matter of getting it posted and aligned with the service.
Thanks LanceDelano! Seems, last service build 13.0.1605.489 works exactly as you promised!
But i'm have some question about buttons image quality. (see picture. This screenshot was made from Edge with 200% zoom)
