I guess I just don't understand setting up a dataflow into an entity. No matter what I select, I can't seem to choose a key field. I'm trying to setup a dataflow from an API into one of our entities. Screenshot attached shows what I mean.
If it helps any, I'm bringing in the information through a REST call.
Hi @notj ,
If you are loading into an existing entity then you need to define the key on your entity within CDS first. See the following article for instructions
@HSheild thanks for that. I've made a key, and then in the dataflow I set that field as my unique key. When I refresh my data, I still wipe out all the lookups to this entity. Am I missing a step somewhere?
Hi @notj ,
This is a problem with the data refresh. It deletes the old data and creates new data. This means that it clears lookup fields that point to that data too.
I posted an idea a while ago to get this updated by Microsoft. Please vote
@HSheild I've actually already voted on that haha.
So there really is no way to incrementally update the information? I'm having a hard time understanding what the purpose of setting up a key field is if the data is just going to get wiped no matter what.
What is everyone doing to get around this? I can't imagine everyone is operating on the idea that you can only ever bring in data once and that's it.
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
Check out the winners of the recent 'Can You Solve These?' community challenge!
Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.
Featuring samples like Return to the Workplace and Emergency Response Applications
Features releasing from October 2020 through March 2021