Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowGet inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.
Good morning,
I have a relationship many to one, from TsrResult Links to Timesteps. The Editor shows the correct direction (many to one) but the arrow is not being drown in the correct direction and the measures are showing the results expected by the arrow. The only workaround I found is either puting the relationship as many to many and choose the direction or either putthing the direction in both directions
Solved! Go to Solution.
Hi @GAN2
It can be confusing but one to many or many to one are essentially the same and in a single direction relationship, the relationship always flows from the one to the many side.
https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-relationships-understand
Timesteps, being a dimension table, why would you want the fact table to filter it?
Please follow folling link.
Relationship troubleshooting guidance - Power BI | Microsoft Learn
Solved: the cardinality you selected isn't valid for this ... - Microsoft Fabric Community
Cardinality relationship not correctly applied in Power BI - Search
OR follow below step to troubleshoot your issue:
I think you’re encountering a visual glitch in Power BI with the cardinality relationship between TsrResult Links and Timesteps. Here are a few steps you can try to resolve this:
Verify Relationship Settings: Double-check that the relationship is set correctly as many-to-one in the relationship editor.
Refresh the Data Model: Sometimes, refreshing the data model can resolve visual inconsistencies. You can do this by clicking on the “Refresh” button in Power BI.
Recreate the Relationship: Delete the existing relationship and recreate it. This can help reset any incorrect configurations.
Update Power BI: Ensure that you are using the latest version of Power BI. Updates often include bug fixes that might resolve your issue.
Check for Filters: Ensure that there are no filters or slicers affecting the visual representation of your data.
Use Many-to-Many Temporarily: As you mentioned, setting the relationship to many-to-many and specifying the direction can be a temporary workaround. However, this might not be ideal for all scenarios.
If these steps don’t resolve the issue, it might be helpful to consult the Power BI documentation or reach out to Microsoft support for more detailed assistance.
Hi @GAN2
It can be confusing but one to many or many to one are essentially the same and in a single direction relationship, the relationship always flows from the one to the many side.
https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-relationships-understand
Timesteps, being a dimension table, why would you want the fact table to filter it?
Thanks Danextian. I used the field timestep of that table to make some calculations and I thought that including it in the TsrResults, given the size of it, would be innefficient resourcewise, but I might be mistaken. Anyway, I might rethink the structure of the file
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code FABINSIDER for a $400 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
90 | |
82 | |
65 | |
51 | |
31 |
User | Count |
---|---|
117 | |
116 | |
71 | |
64 | |
46 |