PowerBI Service throwing Duplicate error

[campelliann]

Hi there,

PowerBIservice keeps failing the schedule refresh with the below error, although we dont have any duplicates on the table. After clearing the cache it seemed the issue was resolved, but then it came back. 

Any ideas?

Column '<ccon>Id</ccon>' in Table '<ccon>Tickets</ccon>' contains a duplicate value '<ccon>2016</ccon>' 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.

[Sahir_Maharaj]

Hello @campelliann,

Here are some steps you can take to address this issue:

1. Verify the data: Double-check the data in the 'Id' column of the 'Tickets' table. Ensure that there are no duplicates or conflicting values. Look for any inconsistencies or discrepancies that might be causing the error.

2. Check relationships: Examine the relationships between the 'Tickets' table and other tables in your data model. Confirm that the 'Id' column is correctly used as the foreign key in any many-to-one relationships. If the 'Id' column is involved in relationships, ensure that the relationships are defined correctly and that the data aligns with the relationship requirements.

3. Check primary key constraints: If the 'Id' column is used as the primary key in the 'Tickets' table, ensure that there are no duplicate values in the column. Additionally, verify that the primary key constraints are properly set in your database.

4. Clear cache and refresh: Since clearing the cache temporarily resolved the issue, try clearing the cache again and then refresh the data. Sometimes, cached data or artifacts can cause conflicts, so clearing the cache can help refresh the data and potentially resolve the error.

5. Check data source: If you are connecting to an external data source, such as a database, make sure that the data in the source itself does not contain any duplicates in the 'Id' column. Verify the integrity of the data directly in the data source to rule out any issues from the source itself.

6. Rebuild relationships: In case the issue persists, consider rebuilding the relationships between tables from scratch. Remove all existing relationships and recreate them based on the correct column mappings and cardinality.

7. Split the query: If you are loading data using a complex query or multiple tables, consider splitting the query or loading the data in stages. This approach can help identify which specific part of the query or table is causing the issue. You can then isolate and resolve the problem area.

Let me know if you might need further assistance.

[campelliann]

Hi there, Thank you for your detailed answer. Could incremental refresh be the cause? At least the problem started with it...