[Vtigercrm-developers] Lazy question on webservices.

[Alan Lord]

On 25/09/12 07:03, Vikas Jain wrote:
> There is another check in CRMEntity where only fields with displaytype 2
> is skipped.
> Its in the insertIntoEntityTable API and this is where i think your
> displaytype 2 field is getting removed.

Thanks for this Vikas, That's very helpful. I can see where the type 2 
fields are being dropped.

> If you allow fields with displaytype 2 here in this API then you will
> open up another hole in the edit views
> where a user can create that field using firebug and update the value.
> To avoid this i think you will need
> an interface where you can filter out displaytype 2 fields from the CRM
> edit pages and then save the records.
> Let me know if this works.

As the update between the external system & vtiger, are only going to 
happen once per week, as a short-term "hack" in our cron script, we 
could simply replace the crmentity.php file before the synchronisation 
job runs (to allow displaytype 2 fields) and then switch it back again 
afterwards... I know this is a bit hacky, but it would probably do the 
trick ;-)

>     the name "displaytype" does not imply the field itself is read only
>     - just that it gets "displayed" in different ways.
>
> Your point seems to be valid and these fields should be allowed to be
> updated from REST, I'm trying to think of
> use cases that might be affected by allowing this displaytype 2 fields
> to be updated and their consequences.

I look forward to hearing your thoughts on this.

Thanks

Alan