In Patchworks, are used to ensure that data pulled from fields in a source system, is mapped to the correct fields in a given destination system.
When you for a service, Patchworks makes life simple by providing lists of standard fields for the associated source and destination systems. Additionally, non-standard, .
NetSuite custom fields work in a very particular way, as summarised below.
The following information relates to the structure of custom field mappings for services where NetSuite is defined as the destination. If you're adding/managing field mappings via the advanced editor (rather than via the dashboard field mapping UI), please keep these details in mind.
Custom fields are organised into parts - for example:
Customer
Customer deposits
Each part includes a customFieldList and this must be referenced in the path specified for a mapping. The example below shows how we might map to a custom field named cseg_channel_type:
Here:
1 is the path to the custom fields part (customerDeposits)
2 is the path from the custom fields part to the custom fields list (customFieldList)
3 is the name of the custom field (cseg_channel_type)
The following information relates to the structure of custom field mappings for services where NetSuite is defined as the source. If you're adding/managing field mappings via the advanced editor (rather than via the dashboard field mapping UI), please keep these details in mind.
When pulling records with custom fields, they will be in the following format:
Some custom fields may be dropdown fields - for example:
In this case, the multiple fields would be mapped as:
If custom fields are present in a sub array, the format would be the same from that point. In the example below, we show a custom field in the itemList sub array:
If you are using the to add/manage field mappings, this structure will be reflected as you navigate mappings for custom fields - information in this section may be useful background but you don't need to take any special action.