NetSuite Location To iPaaS.com Mapping Documentation

A NetSuite location can be captured into iPaaS.com as a location. The integration records the location name and description and captures NetSuite-specific location attributes (location type, store-pickup flag, and store fulfillment memo) into NetSuite … custom fields. Locations are a reference record other collections depend on — inventory capture resolves the iPaaS.com location from the NetSuite location, so locations must be established here first.

ID Format

Manual Sync ID Format

Enter the NetSuite location's internal ID on the Manual Sync page.

External ID Format

iPaaS.com records the NetSuite location's internal ID as the external-ID link, so later transfers update the existing location rather than creating a duplicate. This link is what the product inventory collections resolve when capturing per-location inventory.

Deleted Record Support

There is a Delete NetSuite Location TO iPaaS.com collection that removes the linked iPaaS.com location when the NetSuite location is deleted (driven by the external-ID link), when the corresponding delete event is enabled.

Custom Field Support

NetSuite-specific location attributes are captured into iPaaS.com custom fields named NetSuite … (location type, store-pickup flag, store fulfillment memo). Add the matching iPaaS.com custom fields to retain them.

Mapping Collection Status

Status: Enabled (a single Add/Update collection).
Trigger Events: Create and Update. Locations are captured on demand from the Manual Sync page and on the location events enabled in Inbound Data Flows (see NetSuite Connections and Settings).

Duplicate or Conflicting Mappings

None. A single Add/Update collection captures locations.

Supported Child Collections

None.

System Caveats

iPaaS.com Caveats

Locations are a prerequisite for inventory. The product/variant inventory collections resolve the iPaaS.com location from the NetSuite location with GetiPaaSLocationId and skip inventory rows for locations that do not yet exist in iPaaS.com — capture locations before transferring inventory.
Location data type. This collection populates the iPaaS.com Location entity.

Setup Requirements

Sync locations first. Establish locations in iPaaS.com before running product inventory transfers (FROM or TO iPaaS).
NetSuite … custom fields — create the iPaaS.com custom fields for the location attributes you want to retain.
Inbound Data Flows + webhook scripts — enable the NetSuite location events for automatic capture.

Authentication

The integration authenticates to NetSuite using the connection configured for the integration; the webhook scripts that emit NetSuite events are documented in NetSuite Connections and Settings.

Integration Flow

A NetSuite location is captured — on demand (internal ID) or on location events when Inbound Data Flows and the webhook scripts are in place.
The integration creates or updates the iPaaS.com location with its name and description and captures the NetSuite location attributes into the NetSuite … custom fields.

Mappings

Add/Update NetSuite Location TO iPaaS.com

iPaaS.com data type: Location

Captures a NetSuite location into an iPaaS.com location.

Mapping Type	Source Field (NetSuite)	Destination Field (iPaaS.com)	Description
Dynamic Formula	`if (FullName == null \\|\\| FullName == "") return Name; else return FullName;`	Name	Required. The location name — the NetSuite full (hierarchical) name when present, otherwise the simple name.
Field	Name	Description	Optional. The location's simple name, stored as the description.
Field	LocationType_RefName	NetSuite Location Type	Optional. The NetSuite location type (captured to a NetSuite … custom field).
Field	AllowStorePickup	NetSuite Allow Store Pickup	Optional. Whether the location allows store pickup.
Field	StoreFulfillmentMemo	NetSuite Store Fulfillment Memo	Optional. The store fulfillment memo.

Error Handling

Location not captured — if a location is not yet in iPaaS.com, dependent inventory rows are skipped. Resolution: sync the location, then re-run inventory.

Testing & Validation

Test Scenarios

Capture a location. Manually sync a NetSuite location and confirm an iPaaS.com location with the name/description and the NetSuite … attributes.
Inventory dependency. Confirm that after capturing a location, product inventory for that location is no longer skipped.

Validation Checklist

Locations referenced by inventory are established in iPaaS.com.
The NetSuite … location custom fields exist for the attributes you want to retain.

Additional Notes

The location external-ID link established here is what the inventory collections resolve; see NetSuite Inventory Product From iPaaS.com Mapping Documentation and the product-capture docs.
Known limitations are collected in NetSuite Known Limitations.