Currently, when trying to submit a form via REST, you receive a 1006 error code "Field '[X]' not found in form definition" if the field in the payload is not configured in the form. This behavior doesn't appear to be documented anywhere that I can tell other than the actual error message, but this seems like a huge missing feature in terms of establishing parity with other form submit methods such as the Forms 2.0 API which allows you to
addHiddenFields with any valid field, regardless of if it is defined in the form or not. This front-end behavior is a huge advantage over other form libraries as it allows global form solutions to scale easily and would be a welcome addition to the REST behavior as well.
We received a lot of feedback that customers wanted strict validation on their forms to prevent bots from sending in trash data. It is also more difficult on an implementation and troubleshooting for Forms to accept ambiguous values that differ from it's definition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.