[Vtigercrm-developers] chained requirements

[Adam Heinz]

I'd like to avoid casing out specific fields, as that sort of code
violates the principle of least surprise.  How confusing for the
programmers that come after me to see inconsistent behavior for some
fields.

On a related note, I think that only doing field validation in
javascript is dangerous.  What happens when you save an entity via the
web service?

On Tue, Jun 26, 2012 at 12:57 AM, Prasad <prasad at vtiger.com> wrote:
> Adam,
>
> I would suggest handling this in javascript than inducing a custom
> typeofdata.
> There could be many such validation you might want to handle on value
> change for a field.
>
> Regards,
> Prasad