2022
Issue:
The issue of mapping a custom field present under customer in QuickBooks couldn’t be mapped into the Custom field present at Salesforce.
The main reason was with the Type conversion mapping as the custom field type was Sting in QuickBooks and it was of type Double in Salesforce.
The following is the screen shot of the custom field of type Sting in QuickBooks that has to be mapped to another custom field of type Double present in Salesforce.
Solution:
I used the following mapping query in order to convert the Sting to Double at Salesforce instance.
VALUE("DataExtRet[DataExtName[1]/text()='Item Code']/DataExtValue")
The value in the custom field was converted successfully and synchronized to Salesforce instance as shown below
The converted value present in Salesforce.
Overview
Content Tools