The column "PeiodId in the table 'Timesheets' contains a duplicated value.

[GD61]

Hello,

I'm trying to build a report about Project Online Timesheets in Power BI Desktop, but when I refresh the Timesheet table I get the error:

"TimesheetPeriods: The loading has been canceled because an error during the the loading of a previous table"

"Timesheets: Failed to save modifications to the server. The column "PeiodId in the table 'Timesheets' contains a duplicated value. This is no authorized for unilateral columns in a many to one relationship or for columns which are used as primary key"

How an ID can be duplicated ?

How can I correct this issue ?

NB: there is no relationship between these tables.

Thanks for help

[russellclaude]

I got this error, and I fixed it by

1) copying the text of all my new queries to notepad for safe-keeping

2) deleting all of my new queries from the model

3) applying changes

4) copying and pasting me queries one-by-one back into the model, applying changes one by one. You'll want to re-create them in the proper order.

I think this problem stems from the auto-detection of relationships in Power BI/M Query. This did certainly fix my problem, though.

[AgustAX]

I see your post is almost a year old without response. I had the same issue:

--

Column ID in table MyTable contains a duplicate value [MyValue] and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table.

--

Loading this dataentity independently gave no error, removing all relationships from this entity also did not fix the error.

Finally - I removed this table from the dataload - and refreshed everything without any errors. Then I went back and re-enabled the table, hit refresh and it refreshed just this table - and finally no error.

So - it sounds like this is a dubious error that comes because of the order the data is loaded in? Anyways, the error disappeared when the trouble table was removed from the load and then enabled back once everything else had been loaded.

[danextian]

I have a similar issue. Although I have already removed all relationships the problematic table has with other tables, the problem still persisted.