Duplicate Error

[RV]

Hello all,

Since yesterday, I am having an error concerning a duplicate value. However, when I look it up in the source file, there is no duplicate whatsoever. If I delete the row that PowerBI identifies as duplicate, everything works correctly. This is the error I get:

Has anyone come across this issue?

Thank you,

[Ufuk]

Hi,

I'm also having the same issue. I'm merging data from several sources into a single table and sometimes I'm receiving the same duplicate error. Most of the times the refresh completes without any problem. I'm sure there are no duplicates in the merged data sources.

Were you able to fix this issue?

Thanks.

[kcantor]

Have you tried reversing the relationship? I had my reverse on me once and received this error. I checked for duplicates and blanks but found neither. I checked the relationship flow and it had reversed quicker than the magnetic poles in a bad science fiction flick.

In the case of a merged set, you may need to change how you join and which rows you keep. keeping all creates duplicates.

[RV]

This is how I have the relationship -automatically created after the merging. I am not sure I understand what you mean exactly.

[dpfavand]

RV,

Did you ever manage to fix this issue? I'm having a similar issue, but it seems to occur randomly. Sometimes I refresh and it throws the error, sometimes it doesn't.

[v-sihou-msft]

Hi @RV,

Since you have checked there's no duplicated rows in 'Status' table, please check if there's "Case Sensitive" issue which makes POWER BI DESKTOP evaluate rows as duplicates. Please refer to a related thread below:

http://community.powerbi.com/t5/Desktop/Creating-Case-Sensitive-Table-Relationships/td-p/18210

Regards,

[Seth_C_Bauer]

@RV I could be wrong here, but I think you need to make sure you don't have any "blanks" in your data. Have you confirmed this?

[RV]

Thank you for answering quickly. I selected the column in Excel and removed duplicates (no duplicates here). Checked the list and no blanks either.

[RV]

Ok, so the issue is not from the source data but from the Merge. Before merging the queries it seems like it's fine. Once I add the new columns after merging, I get the duplicate. This happened yesterday and today - it used to never happen before.