How to Fix a one-to-many relationship

[EaglesTony]

I have 2 tables.

Table1 has a unique column of EpicKey.

Table2 has a column EpicLink.

There is a 1 to many relationship between Table1 and Table2, meaning EpicKey is in Table2 as EpicLink for multiple records.

When I try to create the relationship of Table1 to Table2 and try to make it One to Many, it is throwing an error "Relationship between EpicKey and EpicLink has the From end cardinality set to One. From end cardinality must always be set to Many, unless the relationship is One-To-One" ??

[lbendlin]

That doesn't sound right.  Please provide samples of both tables.

[EaglesTony]

Here is what I have: 

1) Epics table has a unique key called "Key"

2) EOS table has a key called "EpicsKey" (There are duplicates of this in the table)

3) Epics has a 1-to-Many relationship to EOS table based on Key-->EpicsKey and it is setup as:

    - Table: SOS

    - Column: EpicsKey

    - Cardinality: Many to One(*:1)

    - Table: Epics

    - Column: Key

    - Cross filter direction: Both

I have a 2nd table SOS that needs the same relationship and when I try to set it up the same as above, this is when I am getting an "ambigoous paths" error.

[lbendlin]

Please provide sample data (with sensitive information removed) that covers your issue or question completely, in a usable format (not as a screenshot).
https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-...
Please show the expected outcome based on the sample data you provided.

https://community.fabric.microsoft.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447...

[EaglesTony]

We decided to handle this situation via SQL Stored Procedure that delivers the data.