Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi Team,
I am getting below error , while performing incremental refresh. There are no duplicate values on SQL side. This happens when there is update in the table.
I have set up incremental refresh based on the Last_Updated_Date (For RangeStart and RangeEnd), and same column is used for Detect Changes. Is that causing this error?
I have gone through multiple threads for this issue, but none of them are helping me because for me there are actually no duplicates.
Thank you in advance!
Regards,
Jyoti Pawar
Hi @Anonymous ,
It may be the "Auto-detect relationship" function that is turned on by default. You can check "Manage Relationships" to see if you have connected some tables without your knowledge, and automatically created several very strange relationships. When the only column is duplicated, the automatically created relationships now become "many-to-many. You can disable these unnecessarily created relationships, and turn off the "automatically detect relationships" function.
Best Regards,
Liu Yang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Did changes as you said. But Still im getting the same error. Switched Off incremntal refresh for the table which is throwing that error then it got resolved. But i need to turn on the Incremental refresh for future data.
Will be appreciated if any one provides solution
Hi. A table with a one to many relation cannot have duplicates. Now I'm wondering, do you have a star schema data model? because if you do, your fact won't be a 1 in the relationships so duplications won't matter. The thing is that if you want an incremental dimension you might want to consider reading more about Slowly Changing Dimnesion to handle unique keys. Incremental refresh is usually recommended for fact tables that won't be on the one side of the relationship.
Consider it might happen that you the engine finds a duplicate value that your source is not showing. Consider that any space or lower/upper case that the source is considering different, it will be the same in the data model on Power Bi.
I hope that helps.
Happy to help!
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.