In many cases, values in your database are different from how you receive them, or have to be delivered to another party differently. This is where conversions come in handy.
You can create as many conversions as you please. The below example shows an conversion of external country code to the configuration template code that has to be used when creating the record.
In the header of the card, you can optionally provide a default value which will be used in all cases where the external value cannot be found in the conversion table.
For an explanation of how to use conversions in your definitions, see the CONVEXTTOINT and CONVINTTOEXT functions in the Functions section.
Need more help with this?