The auto-filled data is retained in text field but its throwing the required validation

a!localVariables(
  local!items: { a!map(name: "", email: "") },
  a!cardLayout(
    showBorder: false,
    contents: {
      a!gridLayout(
        headerCells: {
          a!gridLayoutHeaderCell(label: "Name"),
          a!gridLayoutHeaderCell(label: "Email")
        },
        rows: a!forEach(
          items: local!items,
          expression: a!gridRowLayout(
            contents: {
              a!textField(
                label: "Name",
                value: fv!item.name,
                saveInto: fv!item.name,
                /*inputPurpose: "NAME",*/
                required: true
              ),
              a!textField(
                label: "Email",
                value: fv!item.email,
                saveInto: fv!item.email,
                /*inputPurpose: "EMAIL",*/
                required: true
              )
            }
          )
        )
      ),
      a!buttonArrayLayout(
        buttons: a!buttonWidget(label: "Submit", validate: true)
      )
    }
  )
)

This works fine for me with or without the inputPurpose attribute that is specified.

- Which version of Appian are you on?

- Which browser?

Hello, sorry for the late reply, I just ran into this issue myself.

It looks like the problem happens because Appian doesn’t detect when the browser autofills a field. Even though the value appears in the input, Appian doesn’t recognize it as a valid change, so the required field validation still triggers.

The workaround I found is to manually click into the field or interact with it in some way. That seems to prompt Appian to detect the change and clear the validation error. So while it might not be a full-on bug, it’s definitely a limitation in how Appian handles autofilled values.

Hello, sorry for the late reply, I just ran into this issue myself.

It looks like the problem happens because Appian doesn’t detect when the browser autofills a field. Even though the value appears in the input, Appian doesn’t recognize it as a valid change, so the required field validation still triggers.

The workaround I found is to manually click into the field or interact with it in some way. That seems to prompt Appian to detect the change and clear the validation error. So while it might not be a full-on bug, it’s definitely a limitation in how Appian handles autofilled values.