Field-value formats and conventions
Because field values are all transferred as strings, they should be formatted in a way the connector and the ERP sync can agree on. Although the ERP sync will attempt to parse any value it receives to the best of its abilities, most developers will know the pains of trying to reliably parse things like textual date values with no reference to culture or format. For this reason, we highly recommend encoding all values using the provided copy of
CultureDataFormatter in the SuperOffice.ErpSync.Contract assembly, and we will require the connector to be able to parse field values sent from the ERP sync in the same format.
CultureDataFormatter will encode any supported field type inside brackets and with a prefix that determines what data type we’re dealing with.
Strings do not need to be encoded; they can be sent "as is".
|List||List values should use the internal list item ID (as recognized by the connector). Erp Sync will then use
|Checkbox/Boolean||There is no designated method in
Boolean values will be encoded as "[I:1]" or "[I:0]"