Attribute with choice list & 'value must be provided'

[tford]

Support,

Why do attributes with a choice list & "value must be provided' include a drop down value at the end of the list that is UNDEFINED?

If a user tries to select the UNDEFINED value in the drop down list, they do not know of the error until trying to save the BO.

By definition, there is no reason the UNDEFINED value should be on the choice list.

Am I missing anything?

Tom

[tford]

By the way, the error the user gets upon selecting the blank value at the end of the Choice List is "Field Department has invalid type or is not defined."

Tom

[aware_support2]

This is the intended behavior to draw the user attention to an important filed where the user must make a choice. If you want to pre-select a value from the list you can assign the initial value for the attribute to be the same as one of the values in the list.

[tford]

Thanks,

I understand that the message highlights a required field. But why does the Choice List that is presented to the user include a blank line, when if they choose that blank line, they will get an error message upon saving.

Tom

[aware_support2]

To force the user to make a selection manually the initial value must be blank. If the user misses the filed the error message will be displayed.

[tford]

Even if the attribute has:
- an Initial Value defined as: abc
- a choice list of: abc. def, ghi
- value must be provided: checked

The creation & editing forms still produce a drop down list that includes a blank value. That blank value if selected by the user in the above defined configuration will ALWAYS result in an error message.

Does anyone else see where I'm coming from?

Tom

[tford]

The other minor issue is that if the user gets the error message, the system uses the BO attribute name & not the Presentation Label. It would be preferable to the user to see a Presentation Label since the BO name may not make sense to them.

Thanks,
Tom