CMS_INPUT_COMBOBOX stores VALUE and not KEY in CaaS

Author: thischke
Publication Date: 7/20/2023 15:07

Hello,

I use the following CMS_INPUT_COMBOBOX in the metadata:

<CMS_INPUT_COMBOBOX name="md_country_override" useLanguages="no"> <CMS_INCLUDE_OPTIONS type="database"> <LABELS> <LABEL lang="*">#item.name</LABEL> </LABELS> <KEY>iso_3661_2</KEY> <TABLE>my.countries</TABLE> </CMS_INCLUDE_OPTIONS> <LANGINFOS> <LANGINFO lang="*" label=""/> </LANGINFOS> </CMS_INPUT_COMBOBOX>

In the CaaS the following selection is stored:

"metaFormData": { "md_country_override": { "fsType": "CMS_INPUT_COMBOBOX", "name": "md_country_override", "value": { "fsType": "Option", "label": "Czech", "identifier": "6f68cae9-4f09-4908-918a-eed4bd42ba99" } } },

value.label is fine, but I expect to find also the key, in this example CZ.

Seems to me, that setting KEY option in CMS_INPUT_COMBOBOX does not affect the CaaS. Sounds like a bug / missing implementation for me ... or do I miss something?

With friendly greetings

Thorben Hischke