Your Achievements
Level 1
0% to
Level 2
Next /
to gain points, level up, and earn exciting badges like the new Applaud 5 BadgeLearn more!
View All BadgesSign in to view all badges
Open Alert Bar

Form Submit via REST - Allow fields not in form definition similar to Forms 2.0 JS API's addHiddenFields

Form Submit via REST - Allow fields not in form definition similar to Forms 2.0 JS API's addHiddenFields

Status: No plans to build Submitted by Level 2 on ‎01-31-2022 10:45 AM
1 Comment (1 New)

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.

1,071
1 Comment
Steven_Vanderb3
Marketo Employee
Marketo Employee
‎10-13-2022 08:35 AM
‎10-13-2022 08:35 AM
Status changed to: No plans to build

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.

Home