Error 400 v7.2

[telecastg]

The problem with this new enforcement mechanism is in my opinion:

1) Rules are not documented, no matter how much "sense" they might make to the developers, the vast majority of users need to know, without having to dive into the codebase, what these rules are for each type of field and how not to "violate" them.


2) They take away one of Espo's greatest strength which is its ease of customization, not just by coding but by very userf friendly facilitiess like BPN, workflows and formula.

[yuri]

> Rules are not documented.

What exactly is not documented. Please provide concrete example what is not documented and what is not clear.

[yuri]

> They take away one of Espo's greatest strength which is its ease of customization.

This is a manipulation (that I don't like).

The validations exposed customizations made not properly. After fixing them all will be working. Fixing them should not be a big deal.


* Read-only fields are stripped when posting forms.
* Enum fields accept only values explicitly allowed for the field.
* ID values should match the defined regexp pattern (that you can change in metadata).

Are these making Espo less customizable?

[telecastg]

UPDATE: This issue has been successfully resolved by allowing the back end field validation feature to be controlled by the user, not just by the system defined criteria, in keeping with Espo's tradition of great ease of customization.

Big Thanks !

https://forum.espocrm.com/forum/developer-help/developer-tutorials/88484-how-to-disable-back-end-field-validation-to-avoid-the-field-validation-error#post88498

[abisbe]

Awesome! Big thanks telecastg

[telecastg]

You're welcome abisbe