Forum Discussion
Use Network Graph by Powerviz to create entity/shareholder hierarchy with ownership percentage
Hi celine_84
Since Network Graph by Powerviz is an external visual and not a native Microsoft visual, the community here cannot fully confirm compatibility. The best approach is to check directly with the vendor’s support and documentation.
You can reach it or from marketplace :
or by the link:
https://powerviz.ai/contact-usIf this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi celine_84 , Thank you for reaching out to the Microsoft Community Forum.
The issue you’re seeing happens because the visual treats each node code as a single unique point. When you add paths, entities like 020163 still appear only once, so their children won’t connect under every branch they belong to. You need to clone node instances for each distinct ownership path while keeping the original code as a label.
In practice, when you unfold ownership paths in Power Query or your database, generate a unique ID per node per path. Use these unique IDs as the node keys in the Network Graph and use the original codes only as labels. This allows the same entity to appear in multiple branches, preserving every ownership route correctly.
You can then filter by the root shareholder to show only the edges and node instances from paths starting with that shareholder. This avoids the split effect you see now, because each ownership path is visually distinct but still labelled with the true entity codes.
Community SupportHi celine_84 , Thank you for reaching out to the Microsoft Fabric Community Forum.
To build a shareholder–entity hierarchy in Network Graph by Powerviz, provide only direct ownership links in a Source -> Target format, with optional % ownership. You should not include indirect rows or a level column, since the visual already reveals deeper levels as you expand nodes. Adding pre-calculated levels can create duplicate edges and clutter the graph.
If you want to calculate or filter by hierarchy depth, use DAX’s parent-child functions (like PATH, PATHITEM, PATHLENGTH). These let you explore ownership paths and levels in the data model, while the graph visual stays clean and interactive. In short, keep the model rich with hierarchy logic but feed the visual only direct relationships.
In practice, keep two layers: your Power BI model can use DAX to enrich the hierarchy (for queries, filters or level-based measures), while the Powerviz Network Graph consumes only the clean Source -> Target table with optional ownership weight. This way, the visual remains clear and interactive, while your model still supports more complex ownership analysis.
Understanding functions for parent-child hierarchies in DAX - DAX | Microsoft Learn
Parent and Child functions (DAX) - DAX | Microsoft Learn