Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more
[EDIT] - I found the root cause of the issue : it seems that Power BI Desktop is trimming values and will consider (for instance) :  'AAA  ' = 'AAA' -- which triggers such discrepant behavior where it considers a well-designed Primary Key field as holding duplicates. Power Query is not making this mistake : 
Back End DB (Snowflake) : 2 entries with one having a space in the end
Power Query : 2 distinct rows, normal...
Power BI Desktop, even with this filtering applied :
Deleting the relation already put in place, the data imported from a source of 2 rows end up in a table of 1 row :
-----
[ORIGINAL POST]
Power Bi Desktop detects a duplicate key while refreshing datamodel whereas there is no such duplicate in my dataset - power query itelself does not detect such anomaly (see snapshots attached). The issue did not occur when modeling in Direct Query mode, but appeared when attempting to switch ot either Import or Dual mode.
Refresh : it says "duplicate Key with value " INC."
Full dataset profiling : no duplicates
Column filtering : one single value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.