Summary

iPaaS.com products can be transferred into Microsoft Dynamics NAV through the Product From iPaaS.com mapping collections. The Add collection creates a new NAV item and the Update collection refreshes an existing one; both write to the Microsoft Dynamics NAV Items endpoint.

ID Format

Manual Sync ID Format. To sync a single product on demand, open the subscription's Manual Sync page in the iPaaS.com portal, select the Product From iPaaS.com transfer, and enter the iPaaS.com product SKU. The integration writes this value as the Microsoft Dynamics NAV item number (No.).

Pattern: the iPaaS.com product SKU
Example: 1000

External ID Format. After a successful sync, the Microsoft Dynamics NAV item number (No.) is stored as the external ID that links the iPaaS.com product to its NAV item.

Deleted Record Support

Outbound delete is not supported. Delete is not implemented for products, delete mappings are not included in the default templates, and product deletions in iPaaS.com do not propagate to Microsoft Dynamics NAV.

Custom Field Support

This collection supports custom fields. To populate a Microsoft Dynamics NAV item field that is not in the standard mapping list, add a subscription custom field whose name matches the NAV field name and map its value; the integration adds each such field name and value directly to the request. The name must be a valid field in your NAV environment, or NAV rejects the request.

Mapping Collection Status

Status: Enabled

Trigger Events: Automatic transfers are activated by the subscriber in the iPaaS.com subscription configuration's Outbound Data Flows section, by enabling the iPaaS.com record Create and Update events that should dispatch this collection. No automatic transfer runs until they are enabled there. Manual Sync (see ID Format) is available at any time regardless.

Duplicate or Conflicting Mappings

Other collections that write to the same record. The Product Add and Product Update From iPaaS.com collections both target the same Microsoft Dynamics NAV item. The Product Variant From iPaaS.com collections also write to the NAV Items endpoint (NAV represents variants as flat items), so product and variant transfers share the same item table — keep iPaaS.com SKUs and variant SKUs distinct so the two flows do not write to the same NAV item.

Collision handling. Configurable collision handling is not used for products; it applies only to the Sales Order collections.

Duplicate Matching

A distinct mechanism from collision handling: before creating an item, the integration links to an existing Microsoft Dynamics NAV item matched by SKU (item number) to avoid creating a duplicate, and stores the NAV item number as the external ID.

Supported Child Collections

None for the write to NAV. (Inventory flows in the opposite direction — see the Product To iPaaS.com mapping documentation.)

System Caveats

Microsoft Dynamics NAV Caveats

The Items OData web service must be published in Microsoft Dynamics NAV with the service name exactly Items, or product records cannot transfer.
Order Tracking Policy and Tax Group Code must be valid. The static Tracking Only Order Tracking Policy and the mapped Tax Group Code must exist in the target NAV company, or NAV rejects the item.
Microsoft Dynamics NAV field requirements are governed by your company configuration and are not published in a public API specification. Check your NAV instance for required fields: review your NAV item card for fields marked as required and confirm each is mapped before enabling the collection. Validate field requirements in a staging environment before relying on them in production.

iPaaS.com Caveats

The product SKU is required and becomes the NAV item number; it must be unique.

Setup Requirements

Microsoft Dynamics NAV Configuration

Publish the Items OData web service (Departments → Administration → IT Administration → Services → Web Services), with the service name exactly Items. See the Installation Instructions for the full endpoint setup.

Authentication

The integration authenticates to Microsoft Dynamics NAV using the connection credentials configured in the subscription settings (API Url, Domain, Username, Password, Environment, Company Name). See the Connections and Settings documentation.

Integration Flow

A product is sent from iPaaS.com to Microsoft Dynamics NAV (Add for a new item, Update for an existing one).
The integration checks for an existing NAV item by SKU; if found, it links the records by storing the NAV item number as the external ID.
The item is written to the NAV Items endpoint — created on Add, or merged into the existing item on Update (a partial merge that does not clear unmapped fields).
The Microsoft Dynamics NAV item number (No.) is retained as the external ID for future updates.

Mappings

Add/Update Microsoft Dynamics NAV Product FROM iPaaS.com

iPaaS.com data type: Product

Description. Writes the iPaaS.com product to a Microsoft Dynamics NAV item. The Add and Update collections share the same field mappings; Add creates a new item while Update merges into the matching existing item (a partial merge — empty source values do not overwrite existing NAV data).

Mapping Type	Source Field (iPaaS.com)	Destination Field (Microsoft Dynamics NAV)	Description
Field	`Sku`	No	Key. Sets the NAV item number and is the unique key used to link and update the item. On Update it identifies the existing item.
Field	`Description`	Description	Recommended. Item description.
Field	`Weight`	Net_Weight	Recommended. Item net weight.
Field	`Status`	Status	Recommended. Item status; must be a valid NAV item status.
Field	`TaxClass`	Tax_Group_Code	Recommended. Tax Group Code; must exist in the target NAV company.
Static	`"Tracking Only"`	Order_Tracking_Policy	Recommended. Fixed Order Tracking Policy applied to every item; must be a valid NAV Order Tracking Policy. Change the static value if a different policy is required.

Error Handling

For the catalog of subscriber-visible errors, see the Microsoft Dynamics NAV Error Messages article. NAV rejects an item write when a required field is missing or when the Tax Group Code or Order Tracking Policy value does not exist in the target company; the error names the field.

Testing & Validation

Test Scenarios

Create a new product in iPaaS.com and run the Add transfer; confirm the NAV item is created with the expected number, description, weight, and tax group.
Update a field on an existing product and run the Update transfer; confirm the change appears in NAV and that unmapped fields are preserved.
Attempt a transfer with a Tax Group Code that does not exist in NAV; confirm NAV returns a clear validation error.
Run a manual sync using the product SKU and confirm the correct NAV item is created or updated.

Validation Checklist

The Items web service is published in NAV with the exact service name Items.
The Tracking Only Order Tracking Policy and every mapped Tax Group Code exist in the target NAV company.
Required NAV item fields are mapped or defaulted.

Additional Notes

Variants are written to the same NAV Items endpoint through the separate Product Variant From iPaaS.com collections.
For directionality, required web services, value-replacement, and environment-specific behaviors that apply across collections, see the Microsoft Dynamics NAV Known Limitations article.

iPaaS.com to Microsoft Dynamics NAV Product Mapping Documentation