CB

If no label assume label is value (so existing fields will basically behave as is). Label won't be required.

This CAN be done using language strings and defines, but it shouldn't HAVE to be done this way. For example what if you want to use Digits for the values.. etc..

(BTW, am i allowed to comment and discuss issues? Or is it bad practice)

This feature is really crucial. I remember, i raised a similar question and topic in the forums. Recently i had a need for this type of separated values and labels. You mentioned DIGITS and numbers. That is exactly my task and idea. i.e.:

There is a local club with different membership fees. The current select fields include the name AND price in their value. So, it's really bad for changes and updates, because old members still keep their old field value. More important issue, the value can´t be used for calculations. Even separate display of the "price" is not possible. Workarounds might be to setup new fields like "integer", or even better floats with decimal comma.

Which leads me to my next questions for this feature:

1.) values will be digits/numbers ?
2.) is it possible to have "floats/decimals" as well?
3.) I just know a 3rd party decimal field. Will you include your own? I mean, one that supports labels as well?

Thanks in advance.