Contacts (Contacts) Import Field Mapping Definition

The Contacts (Contacts) import workflow includes one mapping group:

• Contact [Integration point: CONTACT_TO_CONTACT] — See Contact Mapping Group.

Contact Mapping Group

Use the Contact mapping group to map information on the OpenAir contact record with information on the NetSuite contact record. 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 Field Mappings — Overview of default filters and how to modify the default behavior.

• Default Field Mappings — Overview of default field mapping definitions including notes and best practice guidelines where relevant. Information imported by default includes customer internal ID, contact name, email, telephone, and address. Filters are supported.

• Additional Field Mapping — Best practice guidelines for custom field mapping definitions.

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 [SOAP object]	OpenAir Record Type [table]	Mapping Group [Integration point]
Contact [Contact] Schema: Contact (2020.1)|Contact (2023.1) XSD: ContactSearchRowBasic platformCommon (2020.1)|platformCommon (2023.1)	Contact [contact and address] Data Dictionary: contact and address	Contact [CONTACT_TO_CONTACT]

Default and Custom Filters

By default, contact records are imported from NetSuite into OpenAir if the following conditions are all met:

• The Inactive box is NOT checked on the contact record in NetSuite.

• An OpenAir customer record exists matching the customer associated with the contact record in NetSuite, or the customer associated with the project associated with the contact record, if the Import all NetSuite contacts associated with NetSuite projects marked 'Export to NS OpenAir' box is checked on the OpenAir NetSuite Connector administration from .

• The Export to OpenAir [custentity_oa_export_to_openair] box is checked on the contact record in NetSuite. You can modify this behavior to:

  • Import all contacts associated with customers you import from NetSuite into OpenAir by checking the following box on the OpenAir NetSuite Connector administration form: Import all NetSuite contacts associated with NetSuite customers marked 'Export to NS OpenAir'. The Export to OpenAir [custentity_oa_export_to_openair] box is checked on the customer record associated with the contact in NetSuite.

  • Import all contacts associated with projects you import from NetSuite into OpenAir by checking the following box on the OpenAir NetSuite Connector administration form: Import all NetSuite contacts associated with NetSuite projects marked 'Export to NS OpenAir'. The Export to OpenAir [custentity_oa_export_to_openair] box is checked on the project record associated with the contact in NetSuite.

Custom filters are not supported for this mapping group.

Default Field Mappings

The following table describes the default field mapping definitions for the Contact mapping group tab.

NetSuite Field	Direction	OpenAir Field	Notes
Contact.internalID		Contact.netsuite_contact_id	Not visible on field mapping definition table When you import a new contact record from NetSuite into OpenAir, OpenAir stores the internal ID of the NetSuite contact in the NetSuite Contact ID [netsuite_contact_id] custom field. This custom field is used to link the OpenAir and NetSuite records for future updates and matching record associations.
Looked up OpenAir field value — id of OpenAir customer record with netsuite_customer_id equal to the NetSuite field Contact.customer		Contact.customer_id	OpenAir NetSuite Connector looks up the internal ID of the OpenAir customer record matching the NetSuite customer entity associated with the contact in NetSuite. Contact records are not imported if matching associated customer records do not exist in OpenAir and NetSuite.
Contact.entityId		Contact.name	—
Contact.lastName		Contact.last	—
Contact.firstName		Contact.first	—
Contact.email		Contact.email	—
Contact.phone		Contact.phone	—
Contact.fax		Contact.fax	—
Contact.mobilePhone		Contact.mobile	—
Contact.title		Contact.job_title	—
="1"		Contact.active	[Initial Only] By default, the Active box is checked when the Contacts (Contacts) import workflow creates a new contact record in OpenAir. If the Inactive box is checked on the contact record in NetSuite, OpenAir NetSuite Connector does not import the contact into OpenAir — the record is excluded from the integration. Inactive / Active contacts — If the Inactive box is checked on the contact record in NetSuite, OpenAir NetSuite Connector does not import the contact into OpenAir; the record is excluded from the integration. If you clear the Inactive box on the NetSuite contact record, OpenAir NetSuite Connector will import the contact record in the next integration run, and create or update the corresponding contact record in OpenAir according to the field mapping definitions set for the workflow. Checking the Inactive box on the NetSuite contact record does not clear the Active box automatically on the OpenAir contact record. If you check the Inactive box on the NetSuite contact record, clear the Active box manually on the demographic form for this contact in OpenAir.
Contact.billAddress1		Address.address1	Address — Contact addresses are not stored in the contact table in OpenAir but in a separate address table.
Contact.billAddress2		Address.address2	See above
Contact.billAddress3		Address.address3	See above
Contact.billCity		Address.city	See above
Contact.billState		Address.state	See above
Contact.billZipCode		Address.zip	See above
Contact.billCountryCode		Address.country	See above

Additional Field Mapping

Important:

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.

Review the following guidelines:

• The contact entity form in OpenAir includes the Copy customer address box. This is not a field but UI logic to populate the address fields with the current values from the customer record. As this is not a field, you cannot set it using field mapping definition when importing a record. However, you could use advanced field mapping definition to lookup the address of the customer associated with the contact in OpenAir and use the values of the customer address fields to set the contact address fields as part of the Contacts (Contacts) import workflow.