Forum Discussion
Creating Relationships with duplicative values
Hi Anonymous
The issue likely stems from bidirectional filtering in your many-to-one relationship. When relationships are set to filter in both directions, especially in a many-to-one setup, it can cause context propagation issues and inflated aggregations, leading to incorrect calculations like the 27.17 ratio you're seeing. Even though you created a composite key, if the relationship is still ambiguous or if the data model allows both tables to filter each other, Power BI might be duplicating values during evaluation.
Use TREATAS to control context explicitly: Instead of relying on automatic relationship filtering, use TREATAS to apply the correct filter context in your measure.
If you are still facing the issue, it is advisable to reach out to Microsoft Support for better assistance
You can submit a ticket through the Microsoft Power BI Support Portal:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket.
Thanks
Hi Anonymous
Power BI can accurately calculate total values for cross-table ratios, but only when relationships, filter directions, and context are modeled correctly. In scenarios with multiple fact tables or ambiguous filter paths, totals may appear incorrect not due to a system limitation, but due to the underlying data model. If the total still seems off, it's a signal to revisit the model structure. Common fixes include introducing a proper date or country-month dimension table, adjusting relationship directions, or using revised DAX with clearer filter context. With the right design, totals and row-level results will align consistently. It's better to reach out to Microsoft Support for Better Assistance.
If this post helps, kindly mark it as Accepted Solution.
Thank You.
Sorry about that. I dont know how to attached files to a post but here is a wetransfer link again. This is a sample of data. I noticed you had a 3rd table created in your scenario so that could be my problem
Hi Anonymous
Thank you for your patience as we continue to investigate the issue.
I apoligize for the delayed response. Based on our analysis, it seems the unexpected output like the 27.17 ratio you're seeing may be caused by the bidirectional filtering set on a many-to-one relationship within the data model. Bidirectional filters can sometimes lead to ambiguity or unintentional context propagation, causing duplicated values and incorrect aggregations. Although a composite key was introduced, the underlying relationship behavior might still be contributing to the issue.
We are actively refining the data model to ensure accurate results and will keep you updated as soon as we achieve the expected outcome.
In the meantime, could you please test the solution suggested by ABD128 and let us know if it addresses the issue on your end? Your feedback would be very helpful in narrowing down the resolution.
Regards,
Karpurapu D.