Invalid (free-form) select component values?

[shawnbot]

We've discovered some instances (a very small fraction: 64 out of ~100k) of submissions with what appear to be free-form values in a select component using the Choices.js widget. It's not exactly dire because the number of bad rows is manageable, but it could be an issue for us in the long term because data integrity on this field is important.

My hunch is that this is a browser compatibility issue in Choices.js and/or formio.js, and that a JS error is allowing the component to accept whatever value is in the search input. We've been flushing the submissions from form.io to remove PII so I don't have the browser metadata handy, but I'm curious if anyone has seen this before.

[travist]

We have introduced a new validation on Select components that will validate the value to ensure it is a selectable option. It is an optional validation and can be found on the new renderer @

https://monosnap.com/file/uVLw9Bsgp2lunxLgTspTaupUhwERV0

Will this work for your case?

[shawnbot]

@travist That works, but how do I use it? Do we need to upgrade our portal and formio.js?

[travist]

This is part of our 4.13.x release, which is still in RC and we have some known regressions and bugs. Because of this, I would say we need to wait to use it as part of a production release, but if you wish to try it out, then you can upgrade your renderer in your application with this renderer version and then using the Edit JSON feature of the form builder, you will add the following to the select component.

{
  "validate": {
    "onlyAvailableItems": true
  }
}

[olgabann]

We're currently addressing a backlog of GitHub issues. Closing this thread as it is outdated. Please re-open if it is still relevant. Thank you for your contribution!