Dropdown with -- none -- and default value

[mark69]

I defined a field in the dictionary with the choice list specification of "Dropdown with -- none --".

I also set a default value for this field.

When I create a new ticket it displays the selected default value as expected.

If I select the -- none -- value and save the ticket, the field is saved with the default value. This is not what I expect.

Can anyone explain this behaviour?

[Mike Allen]

None is not a choice.   If you want it to be, then create a -- None -- choice and have the value be blank, then set your specification to Dropdown without None..   This will most likely work as you expect.

[mark69]

If I don't specify a default value then the -- none -- value can be saved without problem. So it is a choice.

I will give your suggestion a try.

[zica]

Mark,

If you specified the default value, you cannot save the form with the none value.

I would also say that the Best practice is to select ' value without none ' when you put a default value

What is your exact query to put the value to none   ?

Kind regards,

ZA

Do not feel shy to mark correct or helpful answer if it helps or is correct

[mark69]

I still don't understand why the two options can't be used together.

I set the value to none by clicking on the combo and selecting the -- none -- value. Not much logic involved there