The most smooth way to onboard new partners is found if you can reuse by reusing an already existing format made available by your own developer or by a Bizbrains developer.
...
If the format is not applicable out of the box, Link has some possiblilities to adjust standard (please be aware that this is something the developers should include in the mapping). The advantage is that they don’t need to hardcode it and once done, it can be reused with different data for different partners):
...
The purpose of conversion tables is to convert a given value in the data received/sent to another value in the data going in/out. A perfect example of this is conversion between unit values (e.g. colli to/from cl or piece to/from pce). Description of how to set up new conversion tables: Conversions . For the developer: how to include it in the mapping…
When a conversion table is available, different values can be entered for different partners, and it also supports that one partner uses different values for the same information?.
...
Configuration keys
Configuration keys are used to add data that is not available in the data received from the source system (your ERP, WMS, CRM etc.) to a document for a partner. Examples: EDI Contract Number mandatory by the receiver + ---
...
If a format for at customer is close to an existing format and differences can’t be handled with conversions or configuration keys, the developer can use variants and versions to create new formats based on existing ones. To understand the different building blocks in link, see what we mean by these different expressions see:Link Basic Building Blocks - TDU: kræver korrektur.