You’re offline. This is a read only version of the page.
180
Hello,
How to make sure Opsdate filed modified by SecurityRoleA users?
if user assigned SecurityRoleA the should be able to modify Opsdate filed other it will be disabled.
Thanks,
@Fubar I get that but I replied to the question that the topic starter asked, quoting:
@Shafdev wrote:Hello,
How to make sure Opsdate filed modified by SecurityRoleA users?
if user assigned SecurityRoleA the should be able to modify Opsdate filed other it will be disabled.
Thanks,
Personally, I do agree that FLS is a more efficient way to achieve the scenario but sometimes we're working with customers that are not that flexible and if they need "role" - "fls" is not taken to the final decision.
@a33ik wrote:Hello,
If your requirement is to allow editing specifically for a particular role - then:
- create a JavaScript that will check if the user has the particular role and enable the field (that should be disabled by default);
- develop a sync plugin or real-time workflow that will check if the user that performed the change of the field has the predefined role and throw an exception to prevent the changes if the user doesn't.
In most cases writing custom code for this would be overkill when you could just assign the Security Role and Field Level Security Profile to a Team and assign the users in question to the Team.
The FLS Profile also has the added benefit of being able to specify if the field can be read (user will see a masked field if they do not have permission to view it) and applies to views, forms, API calls.
Hello,
If your requirement is to allow editing specifically for a particular role - then:
You will need to use Field Level security alongside security roles if the user can edit the record but not just the field.
https://learn.microsoft.com/en-us/power-platform/admin/field-level-security
#1
mmbr1606
22
Super User 2025 Season 1
#2
stampcoin
17
#3
ankit_singhal
11
Super User 2025 Season 1
Share
Report
All responses (
Answers (
