cancel
Showing results for 
Search instead for 
Did you mean: 

Upsert (update) capabilities in Power Apps Dataflows

Power Apps Dataflows needs to support upsert (insert and/or update). Currently Dataflows only supports insert/create and delete operations (if enabled). This means that every time a Dataflow is ran will insert duplicate records. If an alternate key is defined then those records will fail during the run because of duplicate key. If delete records is enabled, then all records will be deleted and created per run. There are several keys issues with this:

  1. Upon delete, all history and auditing history are lost
  2. Harder to determine records that changed after a Dataflow run. Modified On will always be the Created On 
  3. Unnecessary triggers (i.e. plugins, flows, workflows, etc) could be invoked upon create and/or delete
  4. Performance: additional redundant delete and create transactions are executed when nothing changed
Status: New
Comments
Frequent Visitor

I second this.

But in addition it also has to support entity delete: what if one entity was deleted in the import source or you decide that you have to deleted it based on rules in dataflow itself?

 

the existing delete capabilities in dataflows are impractical as they will delete all entities which are not visible in the import data flow at the moment of execution, which forces us to always import everything: this cannot scale in any way.

Helper II

I third this.

 

The idea behind a dataflow is fantastic and aligns with Microsofts strategy regarding simplicity and ease of use when working with the Power Platform however this is a massive massive gap and until this is addressed a dataflow is quite limited.