Map NetSuite customer location to customer hierarchy
Check this box to map the customer Location in NetSuite to a customer hierarchy in OpenAir.
-
NetSuite location — The location is a type of classification used to identify, categorize and track records such as financials, transactions, and employees in NetSuite. Locations are useful for wider segments within your business. For more information about locations, see Locations Overview (external link to NetSuite SuiteAnswers | Answer ID: 9845).
Note:After you enable locations for your account, you can create location records and use them to categorise transactions and employees. Classifications are not available for customer and project records as standard in NetSuite. However, you can create a List/Record custom entity field to use locations for customers and projects using a list/record field, if required. See Using Classifications for Customers and Projects in NetSuite.
-
OpenAir hierarchy — You can use hierarchies are used to create multilevel classification trees and categorize records in your OpenAir account. Each hierarchy is associated to one of the following record types: customers, customers, or projects. Multiple hierarchies can apply to the same record type. For more information about hierarchies, see Hierarchy.
After you check this box and you save the integration configuration, OpenAir NetSuite Connector creates the following records in OpenAir:
-
The Customer Location hierarchy. The Customer demographic form in OpenAir will show dropdown fields for the Customer Location hierarchy if it contains any active nodes — Edit the hierarchy record or use form permissions to hide the Customer Location hierarchy dropdown field on Customer demographic form, if required. You can also set the Customer Location as required, and choose to display it as a column on list views.
Note:You can map the NetSuite location to an existing OpenAir hierarchy instead of using the hierarchy created by OpenAir NetSuite Connector. To do so, you need to delete the Customer Location hierarchy created by OpenAir NetSuite Connector and edit the existing hierarchy, hierarchy levels, and nodes in OpenAir. This lets you retain the existing hierarchy you are already using in OpenAir.
-
Custom fields for hierarchy and hierarchy nodes records. These check box custom fields are hidden by default — Edit the custom field records to show them on the hierarchy form, if required.
-
NetSuite location hierarchy [
netsuite_hierarchy_location
] — Check box used to identify if the hierarchy maps to the NetSuite location. -
NetSuite ID [
netsuite_hierarchy_node_id
] — Text custom field used to map each level or node in the OpenAir hierarchy to the corresponding NetSuite location record. -
NetSuite location level or hierarchy node [
netsuite_hierarchy_node_location
] — Check box used to identify if the OpenAir hierarchy level or node maps to a NetSuite location depth level or record.
-
For more information about importing or mapping NetSuite classifications to OpenAir hierarchies, see Importing or Mapping NetSuite Classifications to OpenAir Hierarchies.
If this option is enabled, NetSuite Connector uses software logic associated with the Project form to save changes in OpenAir when importing project records from NetSuite to OpenAir. This has the following consequences:
-
Form scripts associated with the Project form and triggered by an “On submit”, “Before save”, or “After save” event in OpenAir will run for all imported project records. This will impact the performance of your integration runs and may result in errors related to scripting governance limits. You may be able to reduce the performance impact by setting a dedicated integration user and making sure the script do not run if the dedicated integration user executes the script.
-
Form validation in OpenAir will be enforced for all imported project records. A required field with no value or form permission may prevent imported records to be saved in OpenAir. NetSuite Connector will log an error for each imported record that fails to save in OpenAir.