Field validations on Configurable List widget

First, if I only mark a few items with * in a row, the entire Configurable List will be treated as required, then triggering a validation error, that not make sense.

Normally, the Configurable List should be treated as a regular widget, which can set the overall required status. The * markings between items only indicate to these marked items need to be filled out simultaneously in the row.

Hi Netix,

Thanks for reaching out to Jotform Support. When you mark a single field as required within the Configurable List widget, it's expected to trigger a validation error if that specific field is left empty. However, if you only set the Configurable List widget itself as required, the error will go away as long as at least one field inside it is filled out. That’s why having the option to manually set individual fields inside the widget as required is such an important feature.

As for your other question, I've moved that to a new thread. You can check that out here.

Let us know if there’s anything else we can help you with.

Hi John

thanks for your quick replying, but as Configurable List, each row should be considered an independent record, right?

so, inside the config of Configurable List, the "*" means the required fields of each row.

and beyond all rows, there should be another required setting button(like other widgets) to define that whole list should has one record that completed fill these required fields, not raise required fields empty error when whole row is empty(with * field), because that row is not exists.

in the other hand, if some required field is empty but others has value, I agree that the whole Configurable List should raise that error message.

Netix

Hi Netix,

Yes, you're right. In the Configurable List widget, each row is generally treated as an independent record, which means it represents a separate entry with its own set of values. However, as my colleague mentioned, in the Configurable List widget, if you set the entire field as required, the user can pass the field as long as any row within the widget is filled out. However, if you mark a row as required by placing an asterisk (*) in front of its row, the user will be required to complete that specific row, even if the widget itself is not set as required. This is how the Configurable List functions.

Reach out again if there’s anything else we can help you with.

Hi Mahmoud

But the result in my case seems not that way, this first configurable list is set to "not required",

I mark "*" in the first two column of list, when I try to submit the form,

the error messages "" shows.

that's why I confused about the '*' to the row of configurable list,

as you said, that should be considered an empty record, and skip this error since it's not required form fiels.

Netix

Hi Netix,

Even though the Configurable List widget isn’t set as required, some of the individual fields inside it are marked as required. This overrides the overall widget setting. As a result, form can't be submitted unless you add data into those required fields.

Let us know if there’s anything else we can help you with.

Hi John

so, that's my original question, why did non-required configurable list should be blocked cause it has require column in it?

in that screen, it just any empty row there (should take this empty fiield as it's answer)

and no other red star sign on the configurable list field label,

so user will naturally think that can skip till he fill in some row,

and once he fill in, must fill these required columns.

I think that's the key point, the required mark inside configurable list cannot be overwrite the required field widget setting.

He Netix,

I understand that setting this required overrides the required settings through the widget. If you only require a certain configurable list widget fields to be required, then you can set the required settings to No and add the (*) only to the fields that you require on the Configurable Widget. When I tested this, it still requires it even if your Widget Settings are set to no:

Give it a try and reach out again if you have any other questions.

Hi Myla

you just get the same result of mine, so I don't understand if it is reasonable result?

or if there's any possibility to make it more better?

for now, my workaround is set Minimal rows number to 0, though the UX would be a little odd, but works for my scenario.

Hi Netix,

Your point is valid: ideally, an empty row (with required fields marked) should be considered as non-existent and should not trigger validation errors, allowing users to skip rows unless they start filling them out. Currently, this specific behavior is not supported by the widget's validation logic.

Your workaround of setting the minimal rows number to 0 is a practical approach to allow users to submit the form without filling any rows, while still enforcing required fields when rows are added.

At this time, there is no built-in option to separate the required status of individual fields inside the Configurable List from the overall widget's required setting in the way you described. The required mark inside the widget fields will always enforce validation regardless of the widget's overall required setting.

While the feature you're looking for isn't available at Jotform right now, we've gone ahead and escalated your request to our developers. Exactly when or if it's developed depends on their workload, how viable it is, and how many other users also request it. If there are any updates, we’ll circle back to this thread and let you know.

Thanks for your patience and understanding, we appreciate it.