Skip to main content

Microsoft Dynamics NAV to iPaaS.com Product Mapping Documentation

How Microsoft Dynamics NAV items are captured into iPaaS.com as products, including inventory, fields, and requirements.

Summary

Microsoft Dynamics NAV items can be captured into iPaaS.com as products through the Product To iPaaS.com mapping collections. NAV items are polled on a schedule and created or updated as iPaaS.com products, with each item's inventory captured against an iPaaS.com location through child collections and a standalone inventory poll.

ID Format

Manual Sync ID Format. To capture a single product on demand, open the subscription's Manual Sync page in the iPaaS.com portal, select the Product To iPaaS.com transfer, and enter the Microsoft Dynamics NAV item number (No.).

  • Pattern: the NAV item number

  • Example: 1000

External ID Format. The iPaaS.com product SKU (the NAV item number) is stored as the external ID linking the two records. Inventory records are identified by the item number combined with the location (for example, 1000|MAIN).

Deleted Record Support

Not supported. The integration captures products into iPaaS.com only; deleting an item in Microsoft Dynamics NAV is not captured and does not remove the product from iPaaS.com.

Custom Field Support

This collection supports custom fields, allowing additional Microsoft Dynamics NAV item fields to be captured into iPaaS.com product custom fields beyond the standard mappings. (Product Inventory does not use custom fields.)

Mapping Collection Status

Status: Enabled

Trigger Events: Automatic transfers are activated by the subscriber in the iPaaS.com subscription configuration's Inbound Data Flows section, by enabling this collection's events (Poll, Create, and Update). 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 affect the same record. The Product Add and Product Update To iPaaS.com collections both target the same iPaaS.com product. The Product Variant To iPaaS.com collections capture variants as separate iPaaS.com product variants (sharing the underlying NAV Items source). The inventory child collections and the standalone inventory collection all write iPaaS.com product inventory for the same products.

Collision handling. Not applicable (configurable collision handling applies only to the Sales Order collections).

Duplicate Matching

A distinct mechanism: before creating an iPaaS.com product, the integration links to an existing product matched by item number to avoid a duplicate (and links the matching inventory at the Default iPaaS Location). The standalone inventory collection links to an existing inventory record by item-number-and-location.

Supported Child Collections

  • Add Microsoft Dynamics NAV Product Inventory TO iPaaS.com — captures item inventory as part of the Product Add transfer.

  • Update Microsoft Dynamics NAV Product Inventory TO iPaaS.com — captures item inventory as part of the Product Update transfer.

  • Add/Update Microsoft Dynamics NAV Product Inventory TO iPaaS.com (Standalone) — captures item inventory on its own poll, independent of the product transfer.

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 items cannot be polled.

  • Items are read from Microsoft Dynamics NAV; the integration does not create or modify items in NAV through these collections.

iPaaS.com Caveats

  • Name is the item number. The iPaaS.com product Name is set to the NAV item number, not a descriptive name. Remap Name to a descriptive source field if a product name is required in iPaaS.com.

  • Inventory requires a location (reference-data prerequisite). Inventory is recorded against the iPaaS.com location named by the Default iPaaS Location Id For Inventory setting; that location must exist in iPaaS.com (capture it first via the Location To iPaaS.com collection). If the setting is empty, supply a valid iPaaS.com location id on the LocationId mapping, or the inventory cannot be placed.

  • Standalone inventory requires its parent product to already exist in iPaaS.com, or the inventory cannot link.

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.

iPaaS.com Configuration

  • Set Default iPaaS Location Id For Inventory to a valid iPaaS.com location id, and ensure the corresponding location has been captured. See the Connections and Settings documentation.

Subscription Settings — Polling

  • Product Poll Search Days, Product Poll Page Size, Product Poll Date Time Field Override — control the product poll window, page size, and change-detection field.

  • Product Inventory Poll Search Days, Product Inventory Poll Date Time Field Override — control the inventory poll.

  • Poll Time UTC Adjustment — compensates for the Microsoft Dynamics NAV API date-filtering quirk (server-local time vs UTC-stored data).

Authentication

  • The integration authenticates to Microsoft Dynamics NAV using the connection credentials configured in the subscription settings. See the Connections and Settings documentation.

Integration Flow

  1. The scheduled product poll requests items from the Microsoft Dynamics NAV Items endpoint.

  2. For each item, the integration links to an existing iPaaS.com product by item number, or prepares a new one.

  3. The product is created or updated in iPaaS.com, and its inventory is recorded against the Default iPaaS Location (or the mapped location) through the inventory child collection.

  4. The standalone inventory poll independently captures inventory changes for products that already exist in iPaaS.com.

Mappings

Add/Update Microsoft Dynamics NAV Product TO iPaaS.com

iPaaS.com data type: Product

Description. Captures a Microsoft Dynamics NAV item into the iPaaS.com product. The Add and Update collections share the same field mappings; the only difference is the Tracking Method (Add sets it to Product; Update preserves the existing iPaaS.com value).

Mapping Type

Source Field (Microsoft Dynamics NAV)

Destination Field (iPaaS.com)

Description

Field

No

Sku

Required. iPaaS.com product SKU, from the NAV item number.

Field

No

Name

Required. iPaaS.com product Name, set to the NAV item number (see Caveats).

Field

Description

Description

Recommended. Product description.

Field

Unit_Price

DefaultPrice

Required. Product default price, from the NAV item Unit Price.

Field

Net_Weight

Weight

Recommended. Product weight, from the NAV item Net Weight.

Field

Tax_Group_Code

TaxClass

Recommended. Product tax class, from the NAV item Tax Group Code.

Static

"Physical"

Type

Required. Fixed product type.

Static

"Active"

Status

Required. Fixed product status.

Static / Dynamic Formula

"Product" (Add) / DestnationValue.TrackingMethod (Update)

TrackingMethod

Required. Tracking method. Add sets Product; Update preserves the value already on the iPaaS.com product.

Add Microsoft Dynamics NAV Product Inventory TO iPaaS.com

iPaaS.com data type: Product Inventory

Description. Child of the Product Add/Update transfer. Records the item's inventory against an iPaaS.com location.

Mapping Type

Source Field (Microsoft Dynamics NAV)

Destination Field (iPaaS.com)

Description

Field

Unit_Cost

Cost

Recommended. Inventory cost, from the NAV item Unit Cost.

Field

LocationId

LocationId

Required. iPaaS.com location for the inventory; must be a valid iPaaS.com Location. Resolves to the Default iPaaS Location Id For Inventory setting when set; otherwise supply a valid iPaaS.com location id.

Field

Inventory

QtyAvailable

Recommended. Quantity available, from the NAV item Inventory quantity.

Field

Inventory

QtyOnHand

Recommended. Quantity on hand, from the NAV item Inventory quantity.

Add/Update Microsoft Dynamics NAV Product Inventory TO iPaaS.com (Standalone)

iPaaS.com data type: Product Inventory

Description. Captures item inventory on its own poll, independent of the product transfer. Resolves the parent product from iPaaS.com.

Mapping Type

Source Field (Microsoft Dynamics NAV)

Destination Field (iPaaS.com)

Description

Dynamic Formula

resolves the parent product from the product portion of the inventory id

ParentId

Required (automatic). Resolves the iPaaS.com parent product from the product portion of the inventory record id (see mapping notes for the formula). The parent product must already exist in iPaaS.com.

Field

Unit_Cost

Cost

Recommended. Inventory cost.

Field

LocationId

LocationId

Required. iPaaS.com location for the inventory; must be a valid iPaaS.com Location (see the Default iPaaS Location Id For Inventory setting).

Field

Inventory

QtyAvailable

Recommended. Quantity available.

Field

Inventory

QtyOnHand

Recommended. Quantity on hand.

Error Handling

For the catalog of subscriber-visible errors, see the Microsoft Dynamics NAV Error Messages article.

Testing & Validation

Test Scenarios

  1. Create an item in Microsoft Dynamics NAV and run the product poll (or a manual sync by item number); confirm the iPaaS.com product is created with its price, weight, tax class, and an inventory record at the Default iPaaS Location.

  2. Update an item's price or inventory in NAV and re-run; confirm the iPaaS.com product and inventory update without duplicating.

  3. With Default iPaaS Location Id For Inventory unset, confirm inventory cannot be placed; set it to a valid captured location and confirm inventory lands.

  4. Run the standalone inventory poll for an item whose product already exists in iPaaS.com and confirm the inventory updates.

Validation Checklist

  • The Items web service is published in NAV with the exact service name Items.

  • The Default iPaaS Location Id For Inventory points at a captured iPaaS.com location.

  • Product Name is remapped if a descriptive name is required.

Additional Notes

  • Variants are captured separately through the Product Variant To iPaaS.com collections.

  • For directionality, required web services, and environment-specific behaviors that apply across collections, see the Microsoft Dynamics NAV Known Limitations article.

Related Documents

Did this answer your question?