Mapping OpenAir Fields and NetSuite Fields

OpenAir NetSuite Connector lets you map OpenAir fields to NetSuite fields for each integration workflow. To view or modify field mappings, go to Administration > NetSuite Connector > Mapping and select a workflow. See also Adding and Managing Integration Workflows.

Field mapping definitions are organized into mapping group subtabs. Each mapping group subtab corresponds to a specific record type or hierarchy (category) with a different field mapping definition table. The following table provides a quick reference to field mapping definitions on the Mapping tab.

You cannot make any change to the field mapping for an integration workflow if this workflow is included in a workflow group selected for an active scheduled integration run, or if the corresponding OpenAir record type is selected for an active real-time integration. See Protected workflows.

1	Mapping group subtabs — Field mapping definitions are organized into mapping groups. Each mapping group corresponds to a specific record type or hierarchy (category). If there are more mapping group subtabs than can be displayed on the screen, click the more icon to view the hidden groups. Mapping group subtab are listed left to right in their order of execution. Click a subtab to view the field mapping definitions for that mapping group. Note: Each mapping group corresponds to an integration point tag in the legacy advanced tag notation. Pullback integration point tags are included in the same mapping group as PUSH integration point tags. See Advanced Mapping and Filter Notation Reference.
2	Filters — You can define filters to integrate only the records that meet specific criteria. Click Filters to view or set filters for the mapping group. The Filters link appears in bold if filters are set. Filters use the advanced tag notation. See Using Filters.
3	Active switch and actions — The first column in the field mapping definition table lets you activate and deactivate, copy, or delete field mapping rows. Click the switch under the Active column header to activate or to deactivate the field mapping defined in that row. Click the copy icon to duplicate the mapping row and add it as a new custom field mapping. Click the delete icon to delete the mapping row.
4	NetSuite field — The second column in the field mapping definition table shows the NetSuite fields. Select a field from the available dropdown options . If the NetSuite field column is the source data (for an import workflow from NetSuite to OpenAir), you can also enter a value. For example, enter ="1" to set the source data as a constant ( 1 in this case). NetSuite fields are listed using the following format: <SoapObjectName>.<fieldName>, where: <SoapObjectName> is the name of the NetSuite SOAP web services object and uses Pascal case convention. <fieldName> is the name of the field and uses Camel case convention. Refer to the NetSuite SOAP Schema Browser for information about NetSuite fields available for mapping — See Schema Reference Documentation. Note: When importing NetSuite transaction records, or pulling back information from NetSuite transaction records, the NetSuite fields are listed as Transaction.<fieldName> when in fact the SOAP web services object corresponding to the related searches are used to fetch the information from NetSuite.
5	Direction — The second column in the field mapping definition table shows an arrow which indicates whether the mapped field data is imported, exported or pulled back: Arrow pointing right on green color background — the mapped field data is imported from NetSuite into OpenAir. Arrow pointing left on green color background — the mapped field data is exported from OpenAir to NetSuite. Arrow pointing right on orange color background — the mapped field data is pulled back from NetSuite when a record is created.
6	OpenAir field — The fourth column in the field mapping definition table shows the NetSuite fields. Select a field from the available dropdown options . If the OpenAir field column is the source data (for an export workflow from OpenAir to NetSuite ), you can also enter a value. For example, enter ="1" to set the source data as a constant ( 1 in this case). OpenAir fields are listed using the following format: <Table_name>.<field_name>, where: <Table_name> is the name of the table in the OpenAir database. <field_name> is the name of the field in the OpenAir database. Refer to the Data Dictionary for information about standard OpenAir fields available for mapping — See Schema Reference Documentation. OpenAir custom fields are available for mapping. Advanced field mapping may be required to ensure that custom field values are formatted correctly, depending on the custom field type. See OpenAir Custom Fields and Field Mapping. Note: The case convention for both table and field names in OpenAir uses lowercase and underscore characters. However, the table names are listed with an uppercase first letter in the field mapping definition tables.
7	Advanced mapping — To view or set your field mapping definitions, click the advanced mapping icon next to the dropdown field for the source data . See Using the Advanced Tag Notation. Note: The source data is the data in the OpenAir field column if you are viewing the field mapping definitions for an export workflow (from OpenAir to NetSuite), or in the NetSuite field column if you are viewing the field mapping definitions for an import workflow (from NetSuite to OpenAir).
	Initial only — The field mapping definitions for import workflows (workflows importing record data from NetSuite into OpenAir) also include a fifth column. Check the box in the initial only column if you want to import the field data only the first time a specific record is imported from NetSuite into OpenAir. The field mapping row is used when the integration creates a record in OpenAir but not when it updates a record already imported.
8	Adding a field mapping row or pullback row — After you add an integration workflow, the field mapping definition table shows the default configuration with all default field mapping rows set to active. You can add new mapping rows and create custom field mapping definitions to suit your business requirements. See Setting Field Mapping Definitions. Click + Mapping row to add a new row and define a custom field mapping. Click + Pullback row to add a pullback row. Pullback rows define field values to be pulled back when a record is created in NetSuite using the integration. You can add a pullback row only for relevant export workflows and for relevant mapping groups.