Hi,
On a form, what is the difference between a read only field and a lock field?
*This post is locked for comments
To get around this you can create a non-interactive user (and assign the privileges needed to it) and make it the owner of the workflow. Non-interactive does not consume a CRM licence, but you need to temporarily assign one to get it pushed into CRM, then remove the licence later see https://docs.microsoft.com/en-us/power-platform/admin/create-users-assign-online-security-roles#create-a-non-interactive-user-account
Thanks Kokulan, but the workflow should always run. It's the manual update of the field I want to control. When I set the field to read-only in the form it is also read-only for the supervisor and therefore not changable. When I set the read-only in the field security, I can't run the workflow as the user because he doesn't have the rights to change the field. So my question is how I should run this workflow as I don't want to run it as the owner of the workflow (because it is dependable on a particular user account)
In your workflow, you could wrap your Update step under a condition and in that condition you could check if the user is in particular team or if its just few users, you could directly check in list of users as well. If the condition not satisfied, it wont try the update.
Hi David,
How would you fix a date field that should be set to today when another field changes but should only be editable by certain users. I have a workflow that updates the field. Because I get an error when I run the workflow as the user (because he doesn't have access to update the field) I would like to run the workflow as the owner of the workflow, but my problem is that this workflow is then dependent on the access and availability of my user account.
Thanks!
Field-level security is useful if you want only certain users to be able to edit a field. It does have a performance impact (normally negligible, but can have an effect if applied to many fields), so if no users should modify a field (for example if you derive it from other values), then it's simpler to make it read-only. However, read-only only applies to changes made via a form, whereas field-level security applies to any changes made (for example programmatically)
Note that Microsoft terminology is confusing in places. Within a Business Rule, the term 'Lock a field' means to make it read-only
You can specify read, update and create access. When you enable read settings in Field Permissions users can read the information.
because field level denial makes it also unreadable. E.g. not only can you not edit the SS number but you can't even read it.
Rather than using Read Only why would you not use Field Level Security to stop users from changing anything on the field?
Locking a field means that we are preventing it from getting deleted from the form.
Read only field means that we can not edit the value of the field.
Locking a field or section is applied when we think that a particular field is mandatory to be displayed on the form and we dont want it to be removed by customization. Similarly, locking a section will prevent that section to be deleted and also will not allow field inside that section to be deleted or modified.
Read only is - as name suggest - when we dont want data to be updated by the user.
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Andrés Arias as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Community Member 2
Christoph Pock 1
