Empty default value in enum field picks the first enum value -Version 7.2.4

[murugappan]

Hi,

We just encountered an peculiar situation after upgrading from 7.1.4 to 7.2.4. We defined an enum field with 6 values but did not select a default value. In version 7.1.4, when we created a record, this enum field value defaults to "none" but in 7.2.4 the value defaults to the first enum value. Is this how it is suppose to work?

Actually we have a special value of space in the list of enum values but the system does not allow us to set this value as a default. How do we force the default value to "none"?

[Kharg]

Just add an empty value to the enum (no spaces, just empty) and use it as default value.

[yuri]

Seems this is related: https://forum.espocrm.com/forum/bug-...ining-entities

[murugappan]

Hi Kharg , it is exacly what we did but the empty value was the last one as it was added as an after-thought. It still picked the first one and not the empty value. So we moved the value to the first spot and it works fine.

yuri, thank you for the update. You were right it is the same bug. We decided not to fix the code to avoid making the same changes in all the instances. We will wait for the fix in future releases. We have never tempered with the original code from the start unless it is a show-stopper. Fortunately we have not faced such a situation. Espocrm is a master piece and thank you for it. For you info i have posted a good review of the software in Capterra.

[murugappan]

yuri thank you for the fix in version 7.2.5 https://github.com/espocrm/espocrm/m...e/149?closed=1