Find keys that avoid one to many relationships

[Anonymous]

Hi

I'm trying to create a 1-to-many relationship between two tables. According to me, it is a valid relationship. But when I try to create the 1-to-many relationship in powerbi I get a message: "This relationship has cardinality many-to-many..." and can't change it to 1-to-many.  I want to filter the data from source, but can't find what data needs to be filtered.

                                                   

I'm trying to find which key is causing the problem, but I can't find it. For this, I've created two Tables in a report:

1) The first, with the list of the keys of table B and the count of the keys from table B.  This show only 1, as expected.

2) The second, with the list of the keys of table A and the count of the keys from table B. This shows 8 and others numbers, as expected.

How can I find the keys causing the trouble?

Thanks!

[v-lid-msft]

Hi @Anonymous ,

How about the result after you follow the suggestions mentioned in my original post?Could you please provide more details about it If it doesn't meet your requirement?

Best regards,

Community Support Team _ Dong Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[v-lid-msft]

Hi @Anonymous ,

There may be multi same value in the column LlaveAtencionDetales of Table A, we can put column LlaveAtencionDetales and the following measure into a table visual to find the rows.

HasMultiSameValueThisColumn =
IF ( COUNTROWS ( 'Atenciones' ) > 1, "YES", BLANK () )

Best regards,

Community Support Team _ Dong Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Tahreem24]

Give a quick try to below step.
1. Create one new table which has only one column let's say KeyValue and it has only unique value from your master table legs say table B.
NewTable column name=values(Table B[Liaveattenciondetail])
2. Now you have 3 tables A, B and above created table let's say C.
3. So join table A with C using one to many and then again connect C to B using many to one.

Now this become kind of star scheme model.

Please give Kudos to this effort and mark it as a solution if it helps.

[Anonymous]

Hi Tahreem

Thanks, but with that I'll end up with three tables. What I need is to get the keys that don't make possible to create the 1-to-many relationships, because that keys are wrong and should not be there, and must be corrected in the data source.

But I can't find any of these keys.

Thanks