Mapping Rules:
- Only Name of the field has to be used – no need for Object name.
- Standard fields of custom object (Name, Id etc.) cannot be used directly. You need to create a formula field that refers to the Name field.
- No spaces allowed. Your mapping should look like QB_Name__c:CustomFieldInvoiceLineOther2
Regarding prefixes:
a. For transaction (Invoices, SO etc.) mappings first mapping is always for the header fields and the rest could be used for both header and line item fields. If you want to set a header fields mapping in all mapping fields other than first – you need to use dot (.) as a prefix. For example .QB_Name__c:CustomFieldOther
b. For numeric* fields prefix number sign (#) must be used, for date fields – exclamation mark (!). For example #QB_Total__c:Amount
c. If both dot and field type prefix should be used – type prefix always goes first and dot goes second, e.g. !.QB_Due_Date__c:DueDate
d. If you need unidirectional mapping – use slashes instead of colons. SF to QB is slash (/) and QB to SF is back slash ().
Important! Not all objects support unidirectional mapping yet. Please check with us if does not work.
(*) If SF field is set as a number – you need to put # as a prefix (no spaces) before mapping. Otherwise if value is blank in QB SF rejects the record.