NetSuite field definitions for import mapping

You can directly map the address fields for the default billing address in Customer records. By mapping these fields, integrator.io creates an address in the addressbook sublist of the Customer record and sets it as the default billing address.

This field is not shown in the list but must be typed in. 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 , the line item is not ignored, and it’s viewable in the created record. If set to false, the line item is ignored and unavailable in the record despite mapping it.

{{img class=screenshot-frame id=1}}

Mappings

If set to true , it attempts to submit records by ignoring all standard and custom fields made mandatory through customization. NetSuite reference.

{{img class=screenshot-frame id=2}}

Mappings

Use this field to define which mapped fields are used as Record Initializers.

{{img class=screenshot-frame id=3}}

Mappings

To add Inventory detail for any record, you need to add subrecord imports and mappings in the subrecord mappings step.

{{img class=screenshot-frame id=4}}

Mappings

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.

{{img class=screenshot-frame id=5}}

Mappings

Print Nlapi Debug Logs mapping in NetSuite

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.

{{img class=screenshot-frame id=6}}

Mappings

If set to true for any sublist, it removes all the previous lines present in that sublist. Import NetSuite line items.

{{img class=screenshot-frame id=7}}

Mappings

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.

{{img class=screenshot-frame id=8}}

Mappings

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.

Similar to Initialize Values. Instead of mapping it manually, you can set this through the mapping settings.

Use this field to Void transactions. Make sure that the import operation is Update.