Greetings -
I know this post is already a couple of years old but I'm just curious if you ever found a resolution. We've implemented a few bogus "null" values, eg "Unassigned", that we add to to the domain to use as a null, but still am surprised I don't see this issue come up more often ... Thanks for letting me know your experiences with this since you posted this issue.
Hi Bob. I didn't resolve this issue. The combo box can start with a <null> value, but once an actual value has been selected, you can't go back to <null>. I expect to migrate our applications to Javascript very soon and hope that this issue will be addressed. In the meantime, it hasn't really been a problem, since those fields really should have non-null values anyway.