Why do non-required custom fields get the first value in the list if the user doesn't select one?
Why do non-required custom fields get the first value in the list if the user doesn't select one? We have at least two custom fields that this occurs with. One is a User Picker, the other is a Dropdown Listbox. Both have a default value of "Select" in Project Administration, but the first value is selected by the system when a new item is created and the user hasn't selected a value. Is there a way to correct this?
Chris Werner
· 50 |
|
Tuesday, January 31, 2012, 9:22:51 PM |
0
|
We cannot seem to reproduce the issue. Is it possible to send us a backup of your database (support at countersoft dot com)? |
||||
|
0
|
I can try, but it will have to wait until tomorrow. I assume you don't want me to send it via email due to size limitations. Is there another option? |
||||
|
0
|
Send an email to support at countersoft dot com |
||||
|
0
|
Ok, I just sent it. |
||||
|
0
|
Ok, the issue is that for non-required custom fields (drop down) a default value must be selected. You can not leave the custom field as "blank" unless you have such entry in the list. |
||||
|
0
|
ANSWER
Right...creating a blank value option will suffice as a workaround for Dropdown Listboxes, but this can't be accomplished with the User Picker. It is my understanding (via a separate email stream with support) that the next release will support blank value defaults. |
||||
|