I can come up with a reason to be able to do this. Now I come across this. But, as always, there could be another way. I do not want the choice to be required, because the obtained value of "empty value" (or 0) has a special meaning, does not contradict other values ββand can be used for such a special, albeit artificially caused case.
I use EF, and I have either /, or by which a valid dropdown gives the key for a related object in a complex model. When a null value is entered, the expectation is that related items are bound to related objects that are visualized and thus checked. When a nonzero value is entered, it is the key value, so the associated object controls are not displayed, and for the parent object, it is enough to have the existing key value ... without requiring the actual binding values ββneeded to create a new child element of the object.
source share