You are viewing limited content. For full access, please sign in.

Question

Question

Forms - Using Other in a Radio throws a submission error that the value is not in the list

Forms
Updated January 21, 2021
asked on January 20, 2021

I have a Radio Button option with Other as a choice which allows them to enter any value into a text field.

Here is how it looks on the submission where it was used

But it throws this error that the value does not belong to the list of choices.

Well of course if I allow Other as an option, it will not be in the list of choices. Isn't that the point?

0 0

Answer

SELECTED ANSWER
replied on January 21, 2021

This is a known bug is 10.3.1, it has been fixed since Forms 10.4.0. The workaround with Forms 10.3.1 is to change the backend validation level for from the Forms Settings dialog to "validate user input" so it will not validate read-only fields on submitting.

0 0

Replies

replied on January 20, 2021

What version of Forms are you using? This looks like a bug, but I'm surprised it hasn't been reported before. Does it happen for any value typed into other? Can you send some examples of values that fail? 

We'll do some testing, it might have to do with the ( ) in the other text messing it up. 

0 0
View 1 previous reply
replied on January 20, 2021

Version 10.3.1.635

I tried copying the form and submitting with a different value. Same error.

I tried change the name of other back to Other, Same error.

The odd thing is that we are successfully submitting the starting form. Then we get the error when trying to submit on the next user task, which shares the same variable and has it set to read-only. So there is no way we could change it, how can we not get this error one moment and then get it the next without any changes to the data?

 

The error happens at the Consent Review, not at the Start. Both forms share the same variable. No modifications have been done to the list in the variable on either form.

0 0
replied on January 20, 2021

The bug lies somewhere in the fact that it's read-only. The backend is trying to validate the choice wasn't changed by the user, but it doesn't recognize the choice as one of the options. 

Shot in the dark, are the options for choices and values on the initial form that's editable the same as on the second form where the field is read only? 

0 0
SELECTED ANSWER
replied on January 21, 2021

This is a known bug is 10.3.1, it has been fixed since Forms 10.4.0. The workaround with Forms 10.3.1 is to change the backend validation level for from the Forms Settings dialog to "validate user input" so it will not validate read-only fields on submitting.

0 0
replied on January 21, 2021

That did the trick! I usually turn this off anyways because it doesn't like JavaScript or calculations and risks causing the entire submission to error out. It is just hard to remember to do it each time you create a new form.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...