web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Is there a way to NOT ...
Power Automate
Answered

Is there a way to NOT upsert a record with Dataverse Update row action?

(0) ShareShare
ReportReport
Posted on by 464

Greetings, all. I am working with the Dataverse Update row action and just noticed it creates records if the record I am trying to update has been deleted. While I can see the value of this in other scenarios, I want to prevent this in certain cases. Does anyone know if this is possible?

 

UPDATE: Here is an idea (idea link) to fix this behavior. Currently, the only workaround is to do a conditional check before updating. Feel free to upvote.

 

EXAMPLE:

Here's my table before I run the Update; I deleted the record with the GUID I'm sending to Power Automate to update:

arpost_0-1718232188779.png

Here's my flow where the RowID is passed to the Update action:

 

arpost_2-1718232317011.png

 

Here's the table after I run the update:

arpost_1-1718232200945.png

 

Categories:
I have the same question (0)
  • Verified answer
    v-yueyun-msft Profile Picture
    Microsoft Employee on at

    Hi , @arpost 

    Yes, If you provide a row Id that doesn't exist or generated with the guid() expression, the action performs an update or insert (upsert) operation, creating a new row with the Id you provide.

    Use a flow to update a row in Dataverse - Power Automate | Microsoft Learn

     

    And if you want to add the condition before "Update a row" action , you can refer to my flow:

    vyueyunmsft_0-1718245623624.png

     

    empty(outputs('Get_a_row_by_ID')?['body']?['error']) 
    false
     
     
     

    If this reply can help you , you can click mark this reply as solution (Accept solution) which can help more people, thanks in advance! 

     

    Best Regards,

    Yueyun Zhang

     

  • arpost Profile Picture
    464 on at

    @v-yueyun-msft, thank you for the reply. So every update in every flow performing an update has to have an additional Get Row + Condition step? Ouch. That's going to add a lot of bloat to my flows.

     

    Is there no way to configure the Update step itself in such a way as to simply error out if no record exists? Or, at minimum, just return nothing?

  • v-yueyun-msft Profile Picture
    Microsoft Employee on at

    Hi , @arpost 

    Thanks for your response!

    According to my search and testing, there seems that it has no setting that can directly configure not to create a new row when the ID does not exist. If you want to avoid it, you may need to add a Get row by id and Condition in front like I did.

     

    If this reply can help you , you can click mark this reply as solution (Accept solution) which can help more people, thanks in advance! 

     

    Best Regards,

    Yueyun Zhang

  • arpost Profile Picture
    464 on at

    Thanks for checking. I've created a Power Automate idea (idea link) for others to upvote to fix this behavior.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 594

#2
Valantis Profile Picture

Valantis 328

#3
David_MA Profile Picture

David_MA 281 Super User 2026 Season 1

Last 30 days Overall leaderboard