Customers (Customers) Export Field Mapping Definition
The Customers (Customers) export workflow includes one mapping group:
-
Customer [Integration point:
OA_CUSTOMER_TO_NS_CUSTOMER
] — See Customer Mapping Group.
Customer Mapping Group
Use the Customer mapping group to map information on information on customer records in OpenAir with customer records in NetSuite. The mapping group supports filters.
For reference information and best practice guidelines, review the following topics:
-
References — Overview of record types in OpenAir and NetSuite with links to the relevant reference material for information about fields available for mapping.
-
Default and Custom Filters — Overview of default filters and how to modify the default behavior, and custom filters. Custom filters are supported for this mapping group.
-
Default Field Mappings — Overview of default field mapping definitions including notes and best practice guidelines where relevant. Information exported by default includes company name, address and currency. Filters and pullbacks are supported.
-
Additional Field Mappings — There are no specific guidelines for custom field mapping definitions in this mapping group. The mapping group does not support custom pullback field mappings, retrieving information from the record created in NetSuite back into OpenAir.
References
The following table gives reference information about the records and fields available for custom field mapping definition with links to the relevant reference material. See also Schema Reference Documentation.
NetSuite Record type [ |
OpenAir Record Type [ |
Mapping Group [ |
---|---|---|
Customer [ Schema: Customer (2020.1)|Customer (2023.1) |
Customer [ Data Dictionary: customer |
Customer [ |
The Customer
SOAP object is used for customer, lead, and prospect records. This is determined by the property Customer.entityStatus
with the value customer
, lead
, or prospect
.
Default and Custom Filters
By default, customer records are exported from OpenAir to NetSuite if the following conditions are met:
-
The Active box is checked on the customer record in OpenAir.
-
The customer record was not already exported —
Customer.exported
is empty. -
The NetSuite Customer ID [
netsuite_customer_id
] custom field is empty OR the Allow objects with a NetSuite ID to be exported during integration run box is checked on the OpenAir NetSuite Connector administration form. See Allow objects with a NetSuite ID to be exported during integration run.
Custom filters are supported for this mapping group. For more information about adding filter conditions, see Using Filters and Filter Definition.
Default Field Mappings
The following table describes the default field mapping definitions for the Customer mapping group tab.
NetSuite Field |
D |
OpenAir Field |
Notes |
---|---|---|---|
|
|
— |
|
|
|
Not visible on mapping definition table |
|
|
|
— |
|
|
|
— |
|
|
|
— |
|
|
|
— |
|
|
|
— |
|
|
|
Active only if the Map country when exporting customers to NetSuite box is checked on the Customers (Customers) export workflow. See Map country when exporting customers to NetSuite. |
|
|
|
Multiple currency — If the Multiple Currency feature is enabled for your NetSuite account, you can export currency information for customers from OpenAir to NetSuite. The primary currency on the NetSuite customer record is set to
|
|
|
|
The Export to OpenAir [ |
|
|
|
Not visible on mapping definition table [Pullback] When you export a new customer record from OpenAir to NetSuite, OpenAir stores the internal ID of the NetSuite customer in the NetSuite Customer ID [ |
|
— |
|
Not visible on mapping definition table OpenAir adds a timestamp for the date and time the record was exported. |
Additional Field Mappings
Review the following guidelines
-
You should contact your OpenAir Professional Services representative if you need to make changes to your integration configuration and field mapping definitions.
-
For advanced mapping usage and best practice guidelines, see Advanced Field Mapping Definition.
-
Familiarize yourself with the NetSuite and OpenAir technical documentation before attempting to set field mapping definitions using the advanced notation — See Schema Reference Documentation.
No specific guidelines