Forum Discussion
AustinK
7 years agoQrew Commander
Have you tried doing this with form rules instead? If you have a ton of forms it can get annoying but if doing it via the field properties isn't working you could try that.
If you have multiple roles that do not need the ability to edit a field do a multiple condition rule. When a user is in the role <their role(s) here>(multiple roles can be added), make read-only <your fields here>. That way when that role is using that form the fields will be read-only, for other roles they can edit them. You can also flip that rule around and do it as "if the user is NOT in the role <role>, make editable <field>" if everyone except a few roles need the ability to edit.
Try that and see if it works. I'm not sure why it is not working for you with field properties.
If you have multiple roles that do not need the ability to edit a field do a multiple condition rule. When a user is in the role <their role(s) here>(multiple roles can be added), make read-only <your fields here>. That way when that role is using that form the fields will be read-only, for other roles they can edit them. You can also flip that rule around and do it as "if the user is NOT in the role <role>, make editable <field>" if everyone except a few roles need the ability to edit.
Try that and see if it works. I'm not sure why it is not working for you with field properties.