When you set an attribute to have choices there are a few things that can happen:
a) Set no initial value, make attribute mandatory
Displays a drop down with no initial value thereby applying mandatory status fine,
Works fine unless you import data that might have values not in the list (OK - Data issue that can be sorted)
b) Set no initial value, make mandatory but allow other values and allow editing
This displays the first value in the choice list, can this not be blank ?
a) If you import data without validation the mandatory value rules will be ignored. But then the data may be inconsistent - according to your own rules.
b) If you specify a default value for the attribute it will be displayed in the box. Otherwise the box will be blank.
In the past, you could not leave the initial value blank for a mandatory choice attribute - that was solved a few builds ago.
However, if you chose 'Value Must Be Provided', 'Other Values Allowed' and 'Allow Users to add and edit choices' while leaving the initial value blank, it will not display a blank field but rather the first choice in the choices list.
Yes, this is how it is currently implemented. If you do not select the 'Allow users to add and edit choices' option, and do not provide an initial value, the field on form will be blank.
Yes, but unfortunately you get a list box control instead of a drop down which really isn't ideal, could this be looked at as a change ? It's more the problem with the list box control, I would rather use a drop down that allows other entries but doesn't allow editing and adding.
To get a dropdown control displayed on form you need to select 'Generate popup' presentation option for the attribute when using 'Other Values Allowed' and 'Allow Users to add and edit choices' options.