This field is not displayed in the list but must be manually entered. It is used in conjunction with Created From when you want to create a NetSuite record by transforming an existing record.
If set to true , it attempts to submit records by ignoring all standard and custom fields made mandatory through customization. NetSuite reference.
Use this field to define which mapped fields are used as Record Initializers. Initializers are applied when the record is created, before any mapping row runs. Don’t use Subsidiary as an initializer on a transaction that also maps a Vendor or Customer: NetSuite sets the subsidiary from that entity when its row is applied, which overwrites the initialized value.
After enabling the OSS feature in NetSuite, it was found that because of the OSS setup, adding certain line-level fields causes body-level fields like Shipping/Billing Address to be reset (due to the subsidiary’s OSS Nexus). Because this is happening internally, integrator.io is sending the body level fields in NetSuite first, then sending the line-level fields (the ones that have been reset are sent as empty to NetSuite, resulting in the error).
Use this field to configure the order of sublist lines.
Note
This mapping uses nlapiInsertLine instead of nlapiselectNewLine.
Users can directly map the address fields of the default shipping address in Customer records. By mapping these fields, integrator.io internally creates an address in the addressbook sublist of the Customer record and sets it as the default shipping address.
Use this to group records by a specific field. The items are grouped by the "items" field, and instead of having 5 Items in the saved record, only 2 are shown.
If set to true, the inventory details of that particular line are ignored.
If set to true for any sublist, it removes all the previous lines present in that sublist. Import NetSuite line items.
If set to "delete" for any sublist, it will delete only a particular line if it is already present in the record. If that line is not present previously, then this mapping does not allow you to create a line for that particular line item.
For this mapping to work as expected, you should check the Use as a key field to find existing lines field.
Only available for Transaction record types. Use this field to save the Address using Subrecord API.
The Use as a key field to find existing lines setting is not a mapping field, but it’s available in the sublist mapping settings. If set, the setting finds the existing sublist line with "<DestinationRecordField (NetSuite)>" as a key field and updates it. If it doesn’t find the existing sublist line, it will create a new line.
If the setting isn’t used, it will simply create a new line for every item present in the data, irrespective of whether the item was previously present or not.
When you want to load or create a NetSuite record in dynamic mode, NetSuite allows you to pass a record initializer in the nlapi call like this:
var r = nlapiLoadRecord('salesorder', 154, { recordmode: 'dynamic' })To achieve this through integrator.io, map the field Use Dynamic Mode to true in the mappings section.
Note
Mapping order in dynamic mode: in dynamic mode, NetSuite applies the mapping rows in order and sets dependent fields as it goes. On a transaction, NetSuite sets the Subsidiary from the Vendor or Customer you map. Map the Vendor or Customer row before the Subsidiary row, don’t include Subsidiary in Initialize Values, and map Location, Department, and Class after both (header rows before line rows). If the Subsidiary row comes first, or Subsidiary is an initializer, the import fails with You have entered an Invalid Field Value <n> for the following field: location (or department or class) even though the value is active and belongs to the mapped subsidiary — NetSuite has put the record on the vendor’s or customer’s primary subsidiary and checks the value against that subsidiary instead. The vendor or customer must also be assigned to the mapped subsidiary in NetSuite (as a secondary subsidiary on its record); if it isn’t, the error names the subsidiary field instead.
Similar to Initialize Values. Instead of mapping it manually, you can set this through the mapping settings.