Hi, <br><br>There is another check in CRMEntity where only fields with displaytype 2 is skipped. <br>Its in the insertIntoEntityTable API and this is where i think your displaytype 2 field is getting removed. <br><br>If you allow fields with displaytype 2 here in this API then you will open up another hole in the edit views<br>
where a user can create that field using firebug and update the value. To avoid this i think you will need <br>an interface where you can filter out displaytype 2 fields from the CRM edit pages and then save the records.<br>
Let me know if this works.<br><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
the name "displaytype" does not imply the field itself is read only - just that it gets "displayed" in different ways. </blockquote>Your point seems to be valid and these fields should be allowed to be updated from REST, I'm trying to think of <br>
use cases that might be affected by allowing this displaytype 2 fields to be updated and their consequences.<br> <br><div><br><div class="gmail_quote">On 24 September 2012 13:20, Alan Lord <span dir="ltr"><<a href="mailto:alanslists@gmail.com" target="_blank">alanslists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 24/09/12 08:28, Joe Bordes wrote:<br>
> Hi,<br>
><br>
> Ok, I finally read the conversation thoroughly, which I should have done<br>
> the first time before jumping to conclusions and answering incorrectly.<br>
> I apologize for that.<br>
<br>
</div>No problem - your comments were totally valid :-)<br>
<div class="im"><br>
> If I understand correctly the whole problem stems from the fact that you<br>
> are playing with the readonly field in vtiger_field. This field is<br>
> obsolete and has nothing to do with it anymore.<br>
<br>
</div>Well, not quite no. I was simply trying to write to a bunch of vtlib<br>
modules' fields which I want to set to displaytype = 2 so users can't<br>
mess with them but can read them.<br>
<br>
That the readonly value is obsolete is helpful. I knew it didn't work,<br>
but that is not the same thing. I will ignore that from now on.<br>
<div class="im"><br>
> In 5.3, readonly permissions were introduced and work, but at the<br>
> profile level. So each field gets its readonly status based on the users<br>
> profile.<br>
> If you go into settings > profiles and mark a field as readonly there,<br>
> you will see that it acts as a displaytype=2 for the users in that profile.<br>
<br>
</div>Yes, I was aware of that. I was hoping to be able to avoid this. They<br>
will probably need quite a few profiles and we have quite a few custom<br>
modules with lots of fields which are only for display/analysis and<br>
remain synced with an external system.<br>
<div class="im"><br>
> I have never tried accessing or manipulating a field configured like<br>
> this from REST and different users with different profiles, but I'd say<br>
> it should work correctly. Please give it a try and let us know if that<br>
> works, and also, if I am a little bit more "in line" this time :-)<br>
<br>
</div>You are right. If the webservices connection is by an administrator then<br>
it doesn't matter what profile they have. But this also means we need to<br>
explain to to the users that they need to create a separate admin<br>
account (which isn't such a bad thing) and use it *just* for admin tasks...<br>
<br>
Thanks for the input again. I think we'll have a quick dig around in the<br>
webservices code a bit more and see if we can override displaytype=2<br>
just for REST but if not I was going to use the profile route anyway.<br>
<br>
I still stick by my earlier point though; the name "displaytype" does<br>
not imply the field itself is read only - just that it gets "displayed"<br>
in different ways. Shame it doesn't mean that in reality.<br>
<br>
Al<br>
<br>
<br>
_______________________________________________<br>
<a href="http://www.vtiger.com/" target="_blank">http://www.vtiger.com/</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards<br>Vikas<br>Vtiger Team<br>
</div>