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

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

Jonathan Sanderson — Tue, 03 Jun 2025 07:14:17 GMT

Hi,
Not at the moment, but we only upgraded yesterday.

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

Aksat Parekh — Mon, 02 Jun 2025 15:04:36 GMT

Hi,

Alongside this bug, has your team identified any other major bugs in Appian 25.2?

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

Jonathan Sanderson — Mon, 02 Jun 2025 14:32:51 GMT

Hi Ranjith,

Appian have also confirmed the same to me - "This is a bug and the product team is working on fixing this issue."
Thanks
Jonathan

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

Citha Ranjith — Mon, 02 Jun 2025 13:34:12 GMT

Hi Jonathan Sanderson

Good Day!!!

We also face the same issue in our application. We raised an Appian Support ticket as well. They told like the Appian Product team is already aware of this issue they are working on this as well. May be we can expect this issue resolved as an hotfix later.

Thanks

Ranjith

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

Jonathan Sanderson — Mon, 02 Jun 2025 12:47:58 GMT

Hi,
I have also found this issue today, following upgrade to 25.2 - the issue does not occur in 24.4 which is the version we upgraded from.
Did anyone find a solution to the issue (other than the user clicking in the field)?

I have raised a ticket with Appian to ask if it is the expected behaviour, a bug, or if they can suggest a design solution.

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

mohamed_ilias — Tue, 27 May 2025 15:12:30 GMT

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.

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

Mike Schmitt — Thu, 01 May 2025 14:52:01 GMT

I'm always happy to chat with other devs to lend some expertise, but if it's specifically on the "input purpose" parameter of text fields, then beyond the fact that it's never really required, I must underscore that I am not all that familiar with how it actually works in normal usage for those who use it regularly (since i have used it very little and abandoned any old attempts I may have made in the past), so my insights into this specific feature will be really limited.

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

Aksat Parekh — Thu, 01 May 2025 14:48:15 GMT

Hey Mike, can we have an offline discussion about this? I believe your knowledge can really be a breakthrough for my team. Even a 15-minute session should suffice for us to learn some workarounds.

I look forward to your response at aksat.parekh@globalexcel.com. I appreciate your help!

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

Mike Schmitt — Thu, 01 May 2025 14:27:29 GMT

It's not required, and the times I've tried it, users complain that it makes the form confusing to fill out. This may partly be because it only has the option for "name", while most of the forms in my system would have separate "first name" and "last name" fields. To be fair though, I haven't tried messing with it in a while. But the real answer is, since it's not required, I "prefer" just not using it at all.

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

Aksat Parekh — Thu, 01 May 2025 14:21:14 GMT

That's interesting, Mike. What alternatives do you prefer to use instead of the "input purpose" feature?

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

Mike Schmitt — Thu, 01 May 2025 13:04:12 GMT

If it's easily reproducible in 25.1 then I'd suggest anyone being impacted by it should open a support case with Appian. I don't use the "input purpose" feature much (or at all) in my app so I haven't seen it one way or another yet. And it doesn't seem to work in Interface Designer.

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

Aksat Parekh — Wed, 30 Apr 2025 20:31:23 GMT

My team upgraded to the 25.1 platform and is encountering a similar issue. I look forward to connecting to discuss possible workarounds and collaborating to prioritize a resolution from Appian. Linked profile

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

markc2719 — Wed, 30 Apr 2025 17:53:36 GMT

If this is impacting all customers who have upgraded to 25.1, who has it as an issue in production? We're being told since it is not a prod issue, can't be more than a sev3. Any other customers impacted?

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

Mike Schmitt — Wed, 09 Apr 2025 12:56:25 GMT

I fear Appian will not be very supportive of browser auto-fill functionality, at least when it comes to certain corner cases like you've described here. If you believe the behavior is reproducible and counter to what a user might EVER reasonably expect, however, you might raise a support case with Appian (being sure to describe the exact reproduction conditions) and make them aware at least, in case a minor adjustment to the back-end behavior of the field would improve things.

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

Prabhakaran Rajendran — Wed, 09 Apr 2025 12:54:02 GMT

Hi, it's not the Appian function issue, it's the auto fill (which we use data from browser wallet) feature which we use it in browser in that I'm facing the issue.

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

Mike Schmitt — Wed, 09 Apr 2025 12:40:25 GMT

Can you share the code for just the TextField configuration?

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

Mathieu Drouin — Wed, 09 Apr 2025 12:37:42 GMT

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?