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 Apps / Flow to set Dataverse ...
Power Apps
Answered

Flow to set Dataverse fields to read only

(0) ShareShare
ReportReport
Posted on by 31

Is there a Power Automate action to set Dataverse fields to read only? 

 

Use case: a flow with an Adobe Sign sends a PDF for signature, populating that PDF's fields with data from a Dataverse "Application" table. A second flow has a trigger upon that signature's status being signed, and writes the values of PDF fields filled in by the user back into the Dataverse "Application" table.

 

At this point, because the document was signed and the data in that document constitutes a permanent record, we need the corresponding data in Dataverse to be read only.  Do I have to resort to a workaround like creating a field called "IsSigned" and setting it to Yes when the document is signed, and having IsSigned set to Yes being the condition in a business rule to lock all of the fields in the Application table? (Of which there are over 60 - that would be a nightmare business rule). 

I have the same question (0)
  • Drew Poggemann Profile Picture
    9,287 Most Valuable Professional on at

    Hi @KED,

     

    Couple of things here...

    1.  You could actually inactivate the record (bound action) if you want it to lock all fields as this will happen by default.

    2.  The other approach you mentioned is what I would do if there were a limited number of fields that need to be locked on the entity.  You can update this field through a Power Automate flow.

     

    Hope this helps.  Please accept if answers your question or Like if helps in any way.


    Thanks,

    Drew

  • Verified answer
    EricRegnier Profile Picture
    8,720 Most Valuable Professional on at

    Hi @KED,

    The out-of-the-box method to set a record as read-only is with the Status (statecode) and Status Reason (statuscode). Add a new Status Reason that's associated to the Inactive Status (best to use the classic solution explorer for this). Save all and Publish All. Then in Power Automate, you can set the row as inactive with the standard Update a row Dataverse action.

    EricRegnier_0-1620264957120.png

    Hope this helps!

     

  • Len C Profile Picture
    379 on at

    @EricReigner I want to use custom Processes (Actions and Workflows) to set the Status Reason. I am finding that Status Reason is not available as a field to set in the Update Record action. I have Status Reason placed and visibleon all main forms. Is there some reason why Status Reason cannot be updated?

     

    The only way to set it appears to be with a Business Rule.

  • Drew Poggemann Profile Picture
    9,287 Most Valuable Professional on at

    Hi @LenC ,

     

    Please use the "Change Status" in the workflow to change the status vs. doing in Update Record.

    Screen Shot 2022-03-26 at 3.58.37 PM.png

  • Len C Profile Picture
    379 on at

    You may have just made my working weekend 😆

     

    Thanks!

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 324 Most Valuable Professional

#2
11manish Profile Picture

11manish 193

#3
Valantis Profile Picture

Valantis 138

Last 30 days Overall leaderboard