Forum Discussion
Avoiding circular dependency when adding new columns that have dependencies
Hi avanderhoorn
According to your reference link, how about using ALLNOBLANKROW in a FILTER function when using CALCULATE or CALCULATETABLE?
Also, we need consider the relationship among tables used in these formula.
Could you share me some dataset or pbix including all columns and tables used in the formula above?
Best Regards
Maggie
Hi avanderhoorn
After testing with your pbix, I find it doesn’t cause a circular dependency issue until editing the relationship between table “_FaultMessageTypeOverride_” and “ClientFaultEvents”.
As far as I know, the original relationship based on “ErrorMessage” column in both tables can work well, so maybe you don’t need to change this relationship.
Best Regards
Maggie
I agree that things currently "work" and that they break when I change the relationship between table “_FaultMessageTypeOverride_” and “ClientFaultEvents”, but thats the point.
The current relationship isn't correct. I need the relationship to change to be between _FaultMessageTypeOverride_[ErrorMessage] and ClientFaultEvents[ErrorMessage] to be between _FaultMessageTypeOverride_[ErrorMessage] and ClientFaultEvents[ErrorMessageOverride].
I understand that I might not be able to do what I want to do just via a simple relationship, but I need some way of being able to determine the "FaultType" off the "Overriden" error message.
