Setup - Understanding NetSuite Required Fields and How to Set Up
Included in this article
- Field Level Settings
- Preferred Contact or Lead/Prospect/Customer Form Settings
- Fields That Commonly Require A Default Value
- Concurrent Requests
Required fields are critical to the mapping process as if you do not setup these fields properly, you will often have issues trying to create or update records from the incoming system. Your system administrator should have a list of all required fields.
NetSuite has two ways to make fields required that must be honored by the Bedrock Data integration.
2. Preferred Contact or Lead/Prospect/Customer Form Settings: If a NetSuite field is defined as required on the preferred form for updating an object, Bedrock Data will not be able to create a record if that field has not been mapped in the Bedrock Data Mappings screen.
It is a best practice to set a default value in the Bedrock Data mapping to ensure that records will sync across if the data is not provided by the integrated system(s). When mapping Company fields, you only need the Contact > Lead object to have a default value. See screen shot below for how this should look.
If the record already exists and they are either a Prospect or Customer, then these required fields will already be set and this is why no Default Value is needed in the Bedrock settings.
3. Fields That Commonly Require A Default Value: Depending on your NetSuite configuration there are various required field. Some of the most common fields are listed below with commonly used solutions.
1. Terms: This is a common field that needs to have a default value. Since this field is not something that would be assigned in a marketing system it is usually best to create a one line mapping with default value of None. Be sure to include this value in the options in NetSuite.
2. Entity Status: This is a common field that requires a value to create a lead inside NetSuite. Since this is an important field to qualify a lead it can some times be mapped directly to a marketing status field. However, it is usually less labor intensive to simply add a default value.
NetSuite uses two different types of web services, SOAP and RESTlets.
SOAP is a “concurrent call” language which lets NetSuite customers make only make two (2) concurrent calls at a time.
Bedrock does not consume any concurrent SOAP requests. Instead, we use RESTlets, which use “script usage points” as their accounting mechanism. What this means for you is that, by default, the NetSuite connector will make up to 5 concurrent requests. While we can reduce this number to one concurrent request if you'd like, in general we recommend making 5 concurrent requests to maintain optimal performance.