Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi,
How is it possible to generate this diagram when there are many different parents at the same level?
For example, around 500 different parents at the same level?
Greetings.
Solved! Go to Solution.
Hi @SVSCHO
Generating a diagram—such as a hierarchy or organizational chart—when there are many different parents at the same level (like 500+) poses both visual and performance challenges. Most visual tools, including Power BI’s decomposition tree or hierarchy slicers, struggle to display such a wide structure in a meaningful way because they’re optimized for depth rather than breadth. When you have 500 parent nodes at the same level, the chart becomes cluttered, unreadable, and potentially very slow to render.
To handle this, you should consider aggregating or grouping the parents into higher-level categories where possible (e.g., region, department, type), reducing the number of top-level nodes. Alternatively, filtering or slicing the data dynamically can make it manageable—allowing users to explore only a portion of the hierarchy at a time rather than the full breadth. In tools like Power BI, you might use slicers or drill-down features so users can focus on a subset of parents interactively.
Another technique is to use a network visual (like in Deneb or custom visuals such as the Network Navigator), which can handle many nodes and connections, though this trades off clarity for flexibility. If you need to work with complex and large hierarchies, sometimes exporting the data into specialized tools like Graphviz, yEd, or D3.js-based applications may provide better results than BI tools designed for summary and aggregation.
In summary, when facing many same-level parents, you either need to restructure your data model to support grouping or enhance the UX by enabling interaction-driven exploration rather than showing everything at once.
Hi @SVSCHO
Generating a diagram—such as a hierarchy or organizational chart—when there are many different parents at the same level (like 500+) poses both visual and performance challenges. Most visual tools, including Power BI’s decomposition tree or hierarchy slicers, struggle to display such a wide structure in a meaningful way because they’re optimized for depth rather than breadth. When you have 500 parent nodes at the same level, the chart becomes cluttered, unreadable, and potentially very slow to render.
To handle this, you should consider aggregating or grouping the parents into higher-level categories where possible (e.g., region, department, type), reducing the number of top-level nodes. Alternatively, filtering or slicing the data dynamically can make it manageable—allowing users to explore only a portion of the hierarchy at a time rather than the full breadth. In tools like Power BI, you might use slicers or drill-down features so users can focus on a subset of parents interactively.
Another technique is to use a network visual (like in Deneb or custom visuals such as the Network Navigator), which can handle many nodes and connections, though this trades off clarity for flexibility. If you need to work with complex and large hierarchies, sometimes exporting the data into specialized tools like Graphviz, yEd, or D3.js-based applications may provide better results than BI tools designed for summary and aggregation.
In summary, when facing many same-level parents, you either need to restructure your data model to support grouping or enhance the UX by enabling interaction-driven exploration rather than showing everything at once.
Hi @SVSCHO
Thanks for reaching out on the Microsoft Fabric Community Forum.
Yes, you can use Akvelon Hierarchy Chart with many parents at the same level — technically it will render, but usability, performance, and readability will suffer without filtering or grouping.
Best Practice: Use filters/slicers to limit what’s shown or introduce a grouping layer to reduce visual overload.
Please refer the bellow referance link, which user have faced similer to your's in Microsoft Fabric community.
Hierarchy ~Chart Visual (Akvelon) - same id, multi... - Microsoft Fabric Community
------------------------------------------------------------------------------------------------------------------------------
If this solution works for you, please consider marking it as accepted so others facing a similar issue can benefit too.
Regards,
Akhil.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |