Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Can someone help me understand possible reasons for this error? I have a key on my table based on 13 columns that I'm trying to Merge into. I was able to initially append records (without the key field). Subsequently I created the key with no problem indicating that the combination of the 13 fields on each record is unique. Then I tried to change the dataflow to a merge and upsert the same exact data and I get this error.
Solved! Go to Solution.
For anyone else running into this issue, I concatenated the 13 fields in my source query and created a new column in my target Dataverse table called "Merge_Key". Then instead of creating the key on 13 columns I created it on this 1 new column and the merge operation worked. I don't understand why, but seems to be working now.
For anyone else running into this issue, I concatenated the 13 fields in my source query and created a new column in my target Dataverse table called "Merge_Key". Then instead of creating the key on 13 columns I created it on this 1 new column and the merge operation worked. I don't understand why, but seems to be working now.
Hi @scottexe24
Check the following article, it might be helpful.
Field mapping considerations for standard dataflows - Power Query | Microsoft Learn
According to my understanding on the article, using a combination of fields as an Alternate Key for Upsert operation was supposed to work.
Best Regards,
Jing
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Fabric update to learn about new features.
User | Count |
---|---|
18 | |
5 | |
4 | |
3 | |
2 |