AnsweredAssumed Answered

Progressive profiling breaking on number field

Question asked by a3a88be1ced55d2d37f2cfa819cd4f4fe8a6b2bc on Jan 16, 2018
Latest reply on Feb 1, 2018 by a3a88be1ced55d2d37f2cfa819cd4f4fe8a6b2bc

We're testing progressive profiling on a new form. Everything's working great until the user gets to a field where the field type is number (and the field type it maps to is an integer). For some reason,  on submitting the form, instead of showing the thank you message as it should (it's embedded on a page and our CMS controls the thank you message), it refreshes the page and adds the fields and my submissions as parameters at the end of the URL.

 

We changed the field type to text and that fixed the issue. I'm sure we're not the first people to add a number field to a progressive profiling form -- has anyone encountered that issue before? Were you able to keep the field type as number, or did you need to change it to a dropdown or text field and add validation rules to only accept numerical characters?

 

For now, we're removing it altogether and will add it back in when we have more time to test.

 

Thanks for your help!

Outcomes