I have created a Power Query with subsequent dataflow which created the records in CDS fine except for one thing - it created duplicate records.
I have selected the "Do Not Delete records not in this query" however it just seems to create duplicate records in my CDS environment which isnt ideal when your Power Query has 9000+ records and your existing CDS entity you are using has 30k records.
What I need to occur is:
Is this something I need to amend within my Power Query to only show those with a created on date of today? Or do i need to bring my CDS table into Power Query (if possible) to ensure it knows what records already exist before running its nightly update?
Happy to provide more details to assist further.
Solved! Go to Solution.
I am having the same issue where not able to update record while setting the alternate key.
I sets the alternate key value In CDS key settings as a unique name field. When I runs dataflow again, it giving me error that records already found and then failed.
Could any of you please help to how me to resolve this issue.
Hi @panand99 , this thread has already been closed and resolved. If the answers in here do not give you a resolution can you please open a new thread? Also, can you share some more details? Like screenshots of the error message, your alternative key configuration and also the mapping in the data flow?
From my experience this is as designed since Dataflows does not support update on existing Dataflows where keys were added after. Try creating a new one to see if that helps. You can vote for the feature here: https://powerusers.microsoft.com/t5/Power-Apps-Ideas/Upsert-update-capabilities-in-Power-Apps-Datafl...
I know this is a old question, however, I experienced a similar issue but found that some updates must have taken place that has resolved this issue.
In my case, I have two environments, both CDS (Dataverse) and I need the contact records from Environment A to transfer to Environment B. These are the steps I following to make this happen without causing duplicates to appear in environment B.
1. Create a Key in Environment B in the Contact Table
2. Add a connection in Environment B to Environment A
3. Configure the dataflow (without selecting the delete records option)
That's it, works perfectly for me.
So many events that are happening this month - don't miss out!
Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.
Your chance to join an engaging competition of Power Platform enthusiasts.