Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreThe FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now
I am not understanding why we need to use hierarchy when we can drop associated fields in anyways. If someone can explain the concept of hierarchy vs not using hierarchy?
(bonus question: is there an equivalent forum for SharePoint or any SharePoint experts here?)
Solved! Go to Solution.
Hi @PBInonpro,
Hierarchies are useful for exploring data and creating drill down visuals. There a lot of things that can be made easier if you use hierarchies in Power BI. I have this link that might give you more detailed information:
Did I answer your question? Mark this post as a solution if I did!
A hierarchy is a way of grouping fields, making it easier to add multiple fields to a visual. It has no impact on the data. Here's an article on the topic:
https://radacad.com/what-a-power-bi-hierarchy-is-and-how-to-use-it
Proud to be a Super User!
Hi @PBInonpro,
Hierarchies are useful for exploring data and creating drill down visuals. There a lot of things that can be made easier if you use hierarchies in Power BI. I have this link that might give you more detailed information:
Did I answer your question? Mark this post as a solution if I did!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 52 | |
| 38 | |
| 37 | |
| 19 | |
| 18 |
| User | Count |
|---|---|
| 67 | |
| 66 | |
| 34 | |
| 32 | |
| 29 |