You can insert any number of the same type of a user-defined field, unlike the predefined fields, where there may be only one use per type in the form. You only have to pay attention to a unique use of the export column names.
Labels
User-defined fields usually allow the labeling of the field and the placeholder. In this case, input fields are offered in the editor for all language (variants) of the medium. If you create a form as part of a campaign, only the configured languages of the underlying format are taken into account.
Required language variants are marked by a red dot at the flag.
Note
You do not necessarily have to provide text for all language versions. It is usually sufficient to make entries only for the base languages. For the played out format a suitable entry is selected over appropriate inheritance rules.
e.g.: For
However, should it be expedient, e.g. for a desired local "coloring" of the input field depending on the region, then you can of course additionally fill the corresponding language variants. |
Export column name
The export column of the user-defined fields must be defined by you. Only numbers, letters and hyphens are allowed.
Note
Using the export column names of the predefined fields is not allowed and can lead to errors. Likewise, you may use each custom name only once within a form. |
When exporting, columns with the same export column name will be placed on the same column in the export. This also applies to campaigns where, for example, more than one form is used as part of an Interactive Graphic.
Checkbox
Export natively in export format as a truth value, otherwise as text with the values true|false.
Checkbox with a free text label.
Example:
Date
Export natively in export format or if not supported as text in format <YYYY-MM-DD HH:mm:ssZ>. If supported by the target format, the date will be exported as an daatetime with timezone information to specify the beginning of the date.
Inputfield for a date.
Example:
Dropdown list field
Query a value from a given set. In addition to multilingual input of list entries, an ID per entry can be specified for internal processing at your end, which is then used in the export.
Example:
Floating point field / number field
Provides the input of a (integer) numerical value.
Example:
Text field / multiline text field
Text input as a single-line or multi-line text field.
Examples:
Phone number field
Input line for an additional phone number.
Example:
