Forum Discussion

filiparibeiro's avatar
filiparibeiro
Helper III
3 years ago

Incremental Refresh Error

Hello.

Anyone knows if this could be an error due to the use of incremental refresh in pbi desktop and why?

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

I don't have any duplicates so I don't understand why i get it.

Thanks in advance

Need Help
Show and Tell
Tips and Tricks

2 Replies

  • NaveenGandhi's avatar
    NaveenGandhi
    Memorable Member
    3 years ago

    Hello filiparibeiro 

     

    Can you check the count of ID, just in case to make sure there is no duplication. Do the count check if possible for the source data.

     

    Regards,

    Naveen

     

  • ctmullins's avatar
    ctmullins
    Advocate II
    1 year ago

    I'm experiencing this exact same issue.  Incremental refresh is configured properly (query folding, etc).  RangeStart and RangeEnd filtering on my fact table using a datetime column.

     

    After reading the documentation (several times), my understanding was that it would simply overwrite (delete/insert new) any and all rows that qualify on the datetime column filtering.  If this were true, then I would not have any duplicate rows in my data model.  I have confirmed in SSMS that my actual table only contains one row for a given primary key.  Yet the PBI incremental refresh engine is telling me there are duplicates.

     

    The documentation mentions nothing about honoring any kind of primary key relationships.  The documentation mentions nothing about intelligently identifying rows that have UPDATEd, as distinct from rows that are new and should be INSERTed.

     

    WHY?????