Forum Discussion
Different opinion on design needed
Hi jaryszek,
Thank you for reaching out to Microsoft Fabric Community.
Your proposed model looks good. I would keep the single-direction relationships and the bridge_person_client table and avoid bidirectional relationships as they can lead to ambiguous filtering and duplicate results.
If you only need to show a few client attributes in the contact report, use DAX measures. Only consider creating a flattened reporting table if the report becomes too complex or if you run into performance issues.
Thanks and regards,
Anjan Kumar Chippa
Hi jaryszek,
Thank you for reaching out to Microsoft Fabric Community.
Your proposed model looks good. I would keep the single-direction relationships and the bridge_person_client table and avoid bidirectional relationships as they can lead to ambiguous filtering and duplicate results.
If you only need to show a few client attributes in the contact report, use DAX measures. Only consider creating a flattened reporting table if the report becomes too complex or if you run into performance issues.
Thanks and regards,
Anjan Kumar Chippa
thank you, it is great to have somebody to take a look at my concerns.
