Refresh failed: Duplicate Value

[Anonymous]

Hi,

I'm facing an Issue that the scheduled refresh (6 times a day) of a report published in PBI Service fails from time to time, with the message that I have duplicate values and this is not allowed on the one side of a many-to-one relationship:

(And sometimes it also says that I have blank values)

The mentioned value is always a different one. I checked my DM and there seams to not have this values duplicated in it.

The data source is JIRA (on prem) and is fetched via Web.Contents().

This is the model:

Issues, Countries and ImplementationProjects directly originate from IssuesBase and Transistions (All) originates indirectly from it.

(One reference query to get whole data from JIRA and than duplicate it to extract different tables for a relational view.)

I've seen some posts online where they messed up some relations and got this error. BUT the thing is with my Report, the refresh doesn't fail all the time. It fails probably 1 out of 5 scheduled refreshes (I even have 2-3 days where it not fails and then again days where it fails 2 times).

Does anyone has an Idea what the problem is and how to fix it? Or even trace down what 

[AnkitKukreja]

Hi! @Anonymous 

The error points out towards table "Issues" and column"Dema-3644" if you have checked the column and there are no duplicates, then I would advise you to raise an MS support ticket.

But, with my exp the error is pointing out correctly, I would advise you to connect to this table separately and then from a table view copy these/ get a dump of the output from the source and check if there are any duplicates in the data.

[Anonymous]

Hi @AnkitKukreja,

thanks for your answer. 

Yes, the problem states it is in table "Issues" and the column is "key". Column "key" is used as Primary Key for relation to tables "Countries", "ImplementationProjects" and "Transitions (All)".

"DEMA-3644" is the value that is duplicated (or at least it says it is duplicated). I got dozens of this error messages over the last couple of weeks AND it's always a different value. So it's not a problem with this specific entry.

Also "key" is the internal ID used in JIRA for an object, so this should be unique (at least in the Data Source).

When the error occures the refresh fails, so I have no new data to check if there are any duplicates. And on the next refresh it again works out fine (no error; no duplicates).

[AnkitKukreja]

Hi! @Anonymous 

Then I would advise please raise a support ticket with MS.