Forum Discussion
Sharepoint and SQL Many to One Relation Problem in Composite Feature (Preview)
Anonymous,
This behavior is by design in mixed storage mode. I got the following response from PG:
"By design, cross island relationship is always Many to many for now. For GA of composite model, we will allow a many to one cross island, but even that would still have some restrictions and wont support everything a same source many to one does."
There is a simiar thread for your reference.
https://community.powerbi.com/t5/Issues/Composite-Models-Date-Table-incorrectly-creates-many-to-many/idi-p/488312
Regards,
Lydia
Can you edit the relationship to be 1-*?
There is a possibility where capitalization is causing SharePoint to think that a value is unique but not Power BI. Tough to say, that's a long shot. Any chance you can share data?
I cant edit the relationship, it just says: "The cardinality you selected isn't valid for this relationship".
I read about the problem with case sensivity, but currently im testing with 7 different customers where every value in the SP list is unique. I even used the "Remove Duplicates" in the PowerBI Query to archive unique values, but still I got same problem.
Can you turn off Composite Models in your Preview Features? That will prevent a *-* from being created. Then see what happens. Wonder if there might be some kind of bug.
You could always try to create an Enter Data query and enter your customers manually and try it, this might help track down if it is some weird issue with your query or something.