This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
When I add a value to specify the weights of the nodes (source node weight and target node weight) they become a mess. What I realize is that the values are not summed up so that the node sizes, representing each individual in the network, could grow according to the weight of the agent, even when I choose the sum option in the fields of source node weight and target node weight.What I realized is that the structure of the network is based on the first value of the first connection of the agent in the network (in alphabetical order), thus the size of the nodes does not represent the sum of the value of the agent, that way the network gets distorted and messed up. I would like to know if there is any other way to sum up the values, so the node sizes can correctly correspond to those values.
Hi @Milenaish,
I haven't found any document mentioned node. For your scenario, I'd like to suggest you take a look at row level security.
Reference link:
Power BI – Dynamic Row Level Security – Things you need to know to get it working!
Using Username() in DAX with Row-Level Security
Regards,
Xiaoxin Sheng
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 27 | |
| 25 | |
| 23 | |
| 19 | |
| 14 |
| User | Count |
|---|---|
| 50 | |
| 46 | |
| 19 | |
| 18 | |
| 18 |