Why not required field ...is required?

Topic: Why not required field ...is required? (Read 947 times) previous topic - next topic

Why not required field ...is required?

January 13, 2021, 04:37:31 PM

hello all,
I have a field that contains multiple values, comma separated.
In the add/edit pages I've set this field as Checkbox.

Options list data source: "SELECT DISTINCT id AS value,cat_name AS label FROM categories ORDER BY id ASC".
Validation required is set to False.
Display as: Custom inline.

It all works except when I uncheck all values.
If no checkboxes are checked: the field gets red colored, meaning this field is required. But in this case the field is not required.
Why?
Is this a bug or it is by design and I'm missing something?
Please help.
TIA
Tony

Re: Why not required field ...is required?

Reply #1 – January 14, 2021, 02:24:36 PM

Hello,
I just want to add that this happens ONLY if any checkbox has been checked before.
The problem does not happen if you create a new record and don't touch the checkboxes.
Steps to repeat:

create a new record without selecting any checkbox (you can save normally)
edit the previuos record and select any checkbox (you can save normally)
edit the previuos record and UNselect all checkboxex (you CANNOT SAVE anymore (until you select at least one checkbox))

HTH to find the problem.
TIA
Tony