Mapping template issues with delimiter and allows value

[krabina]

The mapping template feature works if you set values directly in the form definition:
|vallues=a,b,c|mapping template=foo
If the values should come from allowed values of a property and you set
|property=bar|mapping template=foo
then it does not work.

[krabina]

allowed values are shown from the property, but they are not mapped using the template

[gesinn-it-gea]

Can you please share the complete field definitions to be sure we don't miss something. Did you have a chance to test this with a current upstream version of PF?

[krabina]

{{{field|Kategorienschema|input type=tokens|delimiter=;|values=AGRI;ECON;EDUC;ENER;ENVI;GOVE;HEAL;INTR;JUST;REGI;SOCI;TECH;TRAN;|mapping template=MappingKategorien|class=form-control}}}

Template:MappingKategorien:
{{#switch: {{{1}}} |AGRI=Landwirtschaft, Fischerei, Forstwirtschaft und Nahrungsmittel |ECON=Wirtschaft und Finanzen |EDUC=Bildung, Kultur und Sport |ENER=Energie |ENVI=Umwelt |GOVE=Regierung und öffentlicher Sektor |HEAL=Gesundheit |INTR=Internationale Themen |JUST=Justiz, Rechtssystem und öffentliche Sicherheit |REGI=Regionen und Städte |SOCI=Bevölkerung und Gesellschaft |TECH=Wissenschaft und Technologie |TRAN=Verkehr | }}

[krabina]

it seems that in the current master the problem is gone.

[krabina]

No. Problem is still there.

[krabina]

A second issue with mapping template is the following:
If you only select one value, it works: when you enter the form for the page again, it will display the mapped value in the form.

As soon as you select a second value, on the next form edit, the field values are shown, not the mapped values.

[krabina]

The second problem goes away if you don't sepcify a delimiter. This field definition works while the above does not.
{{{field|Kategorienschema|input type=tokens|values=AGRI,ECON,EDUC,ENER,ENVI,GOVE,HEAL,INTR,JUST,REGI,SOCI,TECH,TRAN|mapping template=MappingKategorien|class=form-control}}}