Forum Discussion
Memorable MemberBUG::Relationship cardinality issue
You can start reading here Create and manage relationships in Power BI Desktop - Power BI | Microsoft Learn and then follow the links.
Super UserNote the incomplete relationships. Power BI just isn't sure what's on the "foreign" side of this composite relationship, and it makes guesses. You can change these after the fact.
It may be inconsistent but I wouldn't call it a bug.
- Element115
Please explain what makes you write 'incomplete relationships'? What is incomplete about DimDate[Date]>RWS[DATE] and DimTime[Time]>RWS[TIME]?
- lbendlin
You can start reading here Create and manage relationships in Power BI Desktop - Power BI | Microsoft Learn and then follow the links.
- Element115
Ok so I read the documentation. So what? How does that relate to your comment 'Note the incomplete relationships. Power BI just isn't sure what's on the "foreign" side of this composite relationship, and it makes guesses'?
There is no incomplete or composite anything here. Only 2 simple 1:* relationships between DimDate and DimTime to the fact table RWS using the DATE and TIME fields respectively. I mean, this is 101-star schema stuff. The 2 relationships flow from the dim tables to the fact table, and there is no cycle back, ie all relationships start from the dim tables and are unidirectional towards the fact tables. I mean, it couldn't get simpler than that.
So my question still stands: Why did you write 'Note the incomplete relationships'? What did you mean?
