Make a module read-only except for one field

Hi Bob,

As per the above message, I understood that you want to hide most of the fields in the Accounts module for most of the roles in Sugar.

The approach what you thought is completely fine as it does not require any coding and developer support. If you don't want to even show the fields in the layout, you can see how to set the record views based on the role here. By setting the role-based record views we can hide/show the fields as per our requirement.

Hope this helps:)

Thanks,

PK

https://www.bhea.com

Hi Ramya Katram

Thanks very much.  We don't want to hide the fields.  We want all but one to be read-only. It's easy to make an entire module read-only.  I wondered if there is an easy to make the entire module read-only EXCEPT for one field.

I appreciate your help.

Bob

Okay, there is an option to configure a before_save validation that accepts the change of one particular field only and does not allow to save the record if any other field is changed.

BTW, the validation could be respected by both UI and API - it is possible with Logic Builder configuring tool and would take 15 min to draw solution

However, using out of the box security model for the case articulated seems the best solution, even if setting fields readonly may take 30 min, IMHO 

Okay, there is an option to configure a before_save validation that accepts the change of one particular field only and does not allow to save the record if any other field is changed.

BTW, the validation could be respected by both UI and API - it is possible with Logic Builder configuring tool and would take 15 min to draw solution

However, using out of the box security model for the case articulated seems the best solution, even if setting fields readonly may take 30 min, IMHO 

It is better to configure Access Control List. It has a minor development effort and it affects every component inside SugarCRM.

ACL enhancements are so exciting but scary because of possible consequences at the same time.

Is it reasonable to take the risks of ACL development for saving 30 min of one-time manual work? 

Thank you Dmytro Chupylka.  I agree that using the existing security functionality is best - even if it's a pain. My biggest worry was/is performance. I've worked with other systems that allow field-level security rights and they have a potential to perform slowly as individual security rights are enforced.

Thank you, André.