[Vtigercrm-developers] Record-Level Profile Attributes?

[Richard Hills]

Hi Alan

I have done this on a 5.4 installation in the past. We did this through 
a core code change (hack) and I would agree with you that if your client 
is willing to accept javascript as a solution then this would be a 
better route.

Basically we implemented this just for a couple of fields (which were 
described within a custom configuration file and could not be adjusted 
by users) and allowed editing of these fields only by users in an 
administrator profile, we did look at implementing the ability for the 
fields original editor to update the field however decided against this 
as we would need a new table for tracking the fields original propagator.

If you're looking at doing this for v6 and explore the possibilities of 
overriding classes in order to achieve this I would love to hear about 
your findings as I would ideally like to see something like this in the 
core.

On 10/06/14 05:41, Alan Lord (News) wrote:
> Has anyone needed to do this before?
>
> I could really do with making certain fields in a module read-only but 
> on a per-record basis depending on the value of the field(s). If it is 
> empty or null, make it read/write, but once it has been set to a 
> value, make it read-only for certain Profiles.
>
> I guess it's a little similar to a displaytype 4 but that only works 
> on first creation and is then read-only for everyone; including admin.
>
> My current thinking is to go the Javascript route and handle the 
> read/write that way, but just wondering if anyone else has had to 
> effect something like this before?
>
> Cheers
>
> Al
>


-- 
Richard Hills
TechnologyWise Ltd, Tauranga, NZ
richard at tw.co.nz
www.technologywise.co.nz
ph: +64 (0)7 571 1060
fax: +64 (0)7 571 1061