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.
Hi,
I'm currently facing a circular Depency error working on a Power Bi report. I have one sheet in this report when two columns seem to be stuck in a circular dependency according to the error message.
Here are the to formulas of the calculated columns :
Couverture Collisage = RELATED('colisage'[colisage])/AVERAGEX(RELATEDTABLE('1cid des PF');'1cid des PF'[Quantité code mouvement.2])
Dép = 'Site-Article-Fournisseur'[Couverture Collisage]-1
And here is the circular dependency error message I get :
"Site-Article-Fournisseur[Couverture Collisage], Site-Article-Fournisseur[Dép], Site-Article-Fournisseur[Couverture Collisage]"
Can anyone help me one this please?
Thanks,
Antoine
Solved! Go to Solution.
Antoine,
Well my next try would be to make the model less complex. E.g. the intermediaire table has a 1-1 wit the other table, maybe there is a way to combine them since the fields in both seem similar as well?
Hi Antoine,
how do the relationships look between the different tables : 'colisage', '1cid des PF' and 'Site-Article Fournisseur' Do all tables have primary keys?
Are these 3 the only tables in the model? Do you have filtering in both directions on for all relations in the model (which will lead to ambiguity in the model and circular dependencies)?
Error message says that to calculate couverture collisage, the formula is also taking Dép into account, and not only vice versa, so I think key to solution lies in looking in to the relationships between your tables.
I'm not sure the tables have primary keys (I have not found how to manage primary key directly in PBI).
The relation between tables are the following :
Does it help to understand?
Antoine,
Try disabling bidirectional filtering on at least one of your one2many relationships, by double clicking on relationships and direct them from 1 to many. (default)
Harder to explain why then to try 🙂
The idea goes something like : when calculating your couverture collisage, you allow filtering your S-A-F table by other tables. The moment another table filters the S-A-F table, this contains the dép column. The fact that filtering is possible either through fcid and colisage at the same time adds some ambiguity. Removing the bidirectional filter, would solve this if this is the cause.
good luck!
Thanks for for ideas but I'm afraid it don't work. Any other idea?
Antoine,
Well my next try would be to make the model less complex. E.g. the intermediaire table has a 1-1 wit the other table, maybe there is a way to combine them since the fields in both seem similar as well?
I think the last idea worked, thanks a lot.
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 | |
| 22 | |
| 20 | |
| 14 |
| User | Count |
|---|---|
| 50 | |
| 47 | |
| 23 | |
| 18 | |
| 18 |