Preventing a row update on 'submitted' records

(0) Share

Report

Posted on by JB-10040341-0

Hi everyone.

I'm trying to lock down my application with table permissions, but i can't figure this one out.

Say i have a 'submitted' choice on my table. Once that is set to true, i want to disable any more updates to that record. Is there anyway to do this in power pages that is secure (enforced on the server, not anywhere on the client).

Afaik the only way to effectively secure these records is via a custom plugin? Curious if anyone has a solution for this.

Hope you're all having a good week.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

oliver.rodrigues 9,368 Most Valuable Professional on at

Like (0)

Report
Plug-ins is an option, (classic Workflows as well, might be easier)

Another option here would be:

I am assuming you have a List or Subgrid on the Portal where users are opening the records and edit using Basic Form / Multistep Form

what I would do is create a duplicate of that Form in Read-Only mode

you would have to re-create all relevant JS / Metadata / etc

now back in the List / Subgrid, you can apply a filter and display the correct form

if status == submitted

show read-only version

else

show editable version

if the user is being redirected to a Page, and they know the Page URL, technically speaking they can still reach the URL

you can apply an easy Liquid code that reads the record status and doesn't show the form at all

take a look at this for the filter if you need assistance: Power Apps Portals – Entity List: Conditional Action – Oliver Rodrigues

the options above would happen server-side but at the Portal level, not the Dataverse level, hope this helps

Was this reply helpful? Yes No
Suggested answer

Fubar 8,338 Super User 2025 Season 2 on at

Like (0)

Report

Similar to Olivers resposne...

It depends on your exact scenario. For Web Pages, what we have done in the past is wrapped the form tag in a Liquid if/then and added a check using Liquid (liquid runs server side). We originally did this to stop url substitution (and bookmarking) by the user, we had a readonly form and an edit form, and users could open the edit form for another record and then replace the id in the url and edit a record that should be readonly. e.g.

Liquid to check the status reason (could use fetchxml or direct entity/record access in Liquid)

If ok,

load the form

else

display error

https://learn.microsoft.com/en-us/power-pages/configure/liquid/template-tags#fetchxml

https://learn.microsoft.com/en-us/power-pages/configure/liquid/liquid-objects#entities

For lists and subgrids that directly open a basic form, just used fetchxml filtering on the options (available when you have ticked the Advanced on the Options area in the Power Pages Management App ).

Was this reply helpful? Yes No