Using the OOB function, I made a field (a lookup field) Read Only.
The Business changed its mind and decided to open the field for editing.
Using the same OOB function I unchecked the Read Only box, saved and published the change, yet under the assigned security roles the field is still displaying and behaving as Read Only. The field is behaving properly as a Sys Admin.
I checked and there are no Business Rules or workflows setup against the field. What am I missing?
Hi,
Check if any javascript/Business rule is causing this issue
we are facing something similar where on the editor we say make the field read only and publish but in user interface on the form it is still editable...
any insights?
Hi,
Did you find a solution for this issue? I'm facing the same.
Yes, the are viewing the same form and there no additional field security level applied.
No I haven't, but I'm hoping not to have to go down that route because it's a look up field and I would have to undo the relationships between the entities.
Are you sure that the user is looking at the same form as the System administrator ?
Or that there is some field security level applied?
Hi,
Did you tried to remove the field/publish/add the field again/publish ?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156