NetSuite Alternate Id Type To iPaaS.com Mapping Documentation

A NetSuite alternate-identifier type can be captured into iPaaS.com as an Alternate Id Type. The integration normalizes the type's identifier into a name and records a description. Alternate Id Types are a reference record the product alternate-id collections depend on — the product/variant alternate-id children resolve the iPaaS.com Alternate Id Type by lookup, so these type records must exist first.

ID Format

Manual Sync ID Format

Enter the NetSuite alternate-id type's identifier on the Manual Sync page.

External ID Format

iPaaS.com records the type's identifier as the external-ID link, so later transfers update the existing Alternate Id Type rather than creating a duplicate. The product alternate-id collections resolve these records by the keys external_id / reference_name / mpn (and externalid / refname / mpn on variants).

Deleted Record Support

There is no Alternate Id Type delete collection — these reference records are not removed by the integration.

Mapping Collection Status

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

Duplicate or Conflicting Mappings

None. A single Add/Update collection captures alternate-id types.

Supported Child Collections

None.

System Caveats

iPaaS.com Caveats

Alternate Id Type data type. This collection populates the iPaaS.com Alternate Id Type entity.
Prerequisite for product alternate IDs. The product and variant alternate-id collections resolve the Alternate Id Type by lookup and skip the alternate-id row when the type is not found — establish these types before capturing product alternate IDs.
The name is normalized. The type name is the NetSuite identifier with underscores removed and upper-cased (for example, external_id becomes EXTERNALID).

Setup Requirements

Sync alternate-id types first. Establish these types in iPaaS.com before capturing product/variant alternate IDs (FROM or TO iPaaS).
Inbound Data Flows + webhook scripts — enable the relevant NetSuite 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 alternate-id type is captured — on demand (identifier) or on the relevant events when Inbound Data Flows and the webhook scripts are in place.
The integration creates or updates the iPaaS.com Alternate Id Type with the normalized name and a description.

Mappings

Add/Update NetSuite Alternate Id Type TO iPaaS.com

iPaaS.com data type: Alternate Id Type

Captures a NetSuite alternate-id type into an iPaaS.com Alternate Id Type.

Mapping Type	Source Field (NetSuite)	Destination Field (iPaaS.com)	Description
Dynamic Formula	`Id.Replace("_","").ToUpper()`	Name	Required. The type name — the NetSuite identifier with underscores removed and upper-cased.
Static	`"AlternateId Type From NetSuite"`	Description	Control. A fixed description marking the record's origin.

Error Handling

Alternate Id Type not resolved (downstream) — a product alternate-id row whose type is not present in iPaaS.com is skipped. Resolution: sync the Alternate Id Types first.

Testing & Validation

Test Scenarios

Capture a type. Manually sync a NetSuite alternate-id type and confirm an iPaaS.com Alternate Id Type with the normalized name.
Product alternate-id dependency. Confirm that after capturing the types, product alternate-id rows are no longer skipped.

Validation Checklist

The Alternate Id Types (EXTERNALID / REFERENCENAME / MPN, per your data) are established before product alternate-id capture.

Additional Notes

These types are resolved by the product/variant alternate-id collections in the item-capture docs (Product, Assembly, Non-Inventory, Service).
Known limitations are collected in NetSuite Known Limitations.