BNF for mapping:
<mapping>::==<format_prefix><header_prefix><system1_API_name><delimiter><system2_API_name_or_value>
<format_prefix>::==”!”|”#”|”~”|””
“!” – date fields
“#” – number/currency fields
“~” – not nullable text fields
“” – no format_prefix – regular text fields
<header_prefix>::==”.”|””
“.” – applicable only for transactions objects for mapping starting from the second mapping; must be used for the fields from transaction header
“” – no header_prefix – must be always used for the first mapping in transactional mappings and for all non-transactional mappings; first transactional mapping always used for the fields from transaction header; subsequent transaction mappings (starting from the second one) without header_prefix are used for the fields from transaction line item
<system1_API_name> – API name of the field from the system 1, which credentials are specified in the lines #1 – #5 on the last page of the Company Profile
<system2_API_name_value> – API name of the field from the system 2, which credentials are specified in the lines starting from #6 on the last page of the Company Profile, or value (in case of the usage of the equal sign as a delimiter)
<delimiter>::==”/”|”\”|”:”|”=”
“/” – unidirectional mapping from system 1 to system 2
“\” – unidirectional mapping from system 2 to system 1
“:” – bidirectional mapping between system 1 and system 2
“=” – setting a static string value for the field of system 1
Note: Not all cases are supported for all types of objects and all types of Interweave licenses. If mapping is not supported please check with Interweave customer support.
Examples:
!Due_Date__c:DueDate – bidirectional mapping of the header field Due Date (date type) in the first mapping for some transaction.
!.Due_Date__c/DueDate – unidirectional mapping from the system 1 (e.g., Salesforce) to system 2 (e.g., QuickBooks) of the header field Due Date (Date type) in the second or subsequent mapping for transactions.
#Special_Cost__c\InvoiceLineCustomFieldCost1 – unidirectional mapping from the system 2 (e.g., QuickBooks) to system 1 (e.g., Salesforce) of the line-item field Special Cost (currency type) in the second or subsequent mapping for transactions