If no localisation is used, the node and field names in the form profile also generate the corresponding labels in the form.

However, it is possible to define different label names for each DataCockpit language.

In a first step, a key must be assigned to the fields and nodes. This is done via the source structure node/field attribute "Localization key". The following screenshot shows this for field "item_number" (1). The same can be done for the other nodes and fields, but you don't have to. Note: The name of the key is completely arbitrary.

The second step is to define the label names for the respective DataCockpit languages. To do this, select the submenu item " Localize for DataCockpit/Portal" in the source structure menu (2). The following screenshot shows the dialogue for that.

(3) Key: You can now define a label name and a tooltip for each localisation key for each available language.

(4) profile.name: You can also overwrite the profile name.

(5) Node/Field/Value: If you have defined allowed values for a field, they can be localised as well (which probably would not make much sense in our example).