Formstack form required fields do not validate

Validation fails on fields that are prefilled.

Reviewed March 26, 2024

This issue has been partially fixed.  See below.

The Issue

Formstack forms support validation; e.g. an email field value must be a 'valid email address'. They also support prefilled values, such as when the user's details are already shown in the form: name, email, department...

Recently authors have noticed validation can fail for some prefilled fields.

Workaround

This appears to be a bug with Formstack forms.

One workaround is for the people completing the form to click into each 'invalid' field and gently tweak the information; e.g. typeover the last character of each field value.

Update - We have devolped a partial fix for Formstack form field(s) prefilling using User Info Loader data. Formstack has a new API for its Verson 4 forms. Usage of previous code to handle field populating would insert the data, but Formstack forms would not acknowledge it. This created the current issue where fields would erase upon clicking, or the form saying the field was required when there was data visibly there. This has been fixed in the code deployment of May 2, 2024. However, forms that share the same ID number still cause trouble; e.g. use of Formstacks divided first-name and last-name combo field.

Was This Information Helpful?

(Required)
(Required)
(so we can thank you or request more details)
(Required)
(buffalo.edu addresses only please)
(Required)