Summary
Microsoft Dynamics NAV items can be captured into iPaaS.com as product variants through the Variant To iPaaS.com mapping collections. NAV items are polled and created or updated as iPaaS.com product variants, with each variant's inventory captured against an iPaaS.com location through child collections. Because Microsoft Dynamics NAV has no native variant concept, the parent-product relationship is resolved from iPaaS.com.
ID Format
Manual Sync ID Format. To capture a single variant on demand, open the subscription's Manual Sync page in the iPaaS.com portal, select the Variant To iPaaS.com transfer, and enter the Microsoft Dynamics NAV item number (No.).
Pattern: the NAV item number
Example:
1000-RED-L
External ID Format. The iPaaS.com variant SKU (the NAV item number) is stored as the external ID. Inventory records are identified by the item number combined with the location.
Deleted Record Support
Not supported. The integration captures variants into iPaaS.com only; deleting an item in Microsoft Dynamics NAV is not captured and does not remove the variant from iPaaS.com.
Custom Field Support
Custom fields are not supported for these collections.
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 Variant Add and Variant Update To iPaaS.com collections both target the same iPaaS.com product variant. The variant inventory child collections write iPaaS.com inventory for the same variants. The Product To iPaaS.com collections capture the base products that variants belong to (the parent relationship is resolved from iPaaS.com).
Collision handling. Not applicable (configurable collision handling applies only to the Sales Order collections).
Duplicate Matching
A distinct mechanism: before creating an iPaaS.com variant, the integration links to an existing variant to avoid a duplicate; the variant inventory links by item-number-and-location.
Supported Child Collections
Add Microsoft Dynamics NAV Product Variant Inventory TO iPaaS.com — captures variant inventory as part of the Variant Add transfer.
Update Microsoft Dynamics NAV Product Variant Inventory TO iPaaS.com — captures variant inventory as part of the Variant Update 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
Parent product relationship is resolved from iPaaS.com — the variant's parent product must exist in iPaaS.com for the relationship to be established.
Inventory requires a location (reference-data prerequisite). Variant 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. If the setting is empty, supply a valid iPaaS.com location id on the LocationId mapping.
Setup Requirements
Microsoft Dynamics NAV Configuration
Publish the Items OData web service, service name exactly
Items. See the Installation Instructions.
iPaaS.com Configuration
Set Default iPaaS Location Id For Inventory to a valid captured iPaaS.com location. Ensure parent products are captured in iPaaS.com. See the Connections and Settings documentation.
Authentication
The integration authenticates using the connection credentials in the subscription settings. See the Connections and Settings documentation.
Integration Flow
The scheduled poll requests items from the Microsoft Dynamics NAV
Itemsendpoint.The integration resolves the variant's parent product from iPaaS.com and links to an existing iPaaS.com variant, or prepares a new one.
The variant is created or updated in iPaaS.com, and its inventory is recorded against the Default iPaaS Location through the inventory child collection.
Mappings
Add/Update Microsoft Dynamics NAV Product Variant TO iPaaS.com
iPaaS.com data type: Product Variant
Description. Captures a Microsoft Dynamics NAV item into an iPaaS.com product variant. The Add and Update collections share the same field mappings.
Mapping Type | Source Field (Microsoft Dynamics NAV) | Destination Field (iPaaS.com) | Description |
Field |
| Sku | Required. iPaaS.com variant SKU, from the NAV item number. Must be unique and not equal to the parent product SKU; the parent product must already exist in iPaaS.com. |
Field |
| DefaultPrice | Recommended. Variant default price, from the NAV item Unit Price. |
Field |
| Weight | Recommended. Variant weight, from the NAV item Net Weight. |
Add/Update Microsoft Dynamics NAV Product Variant Inventory TO iPaaS.com
iPaaS.com data type: Product Variant Inventory
Description. Child of the Variant Add/Update transfer. Records the variant's inventory against an iPaaS.com location.
Mapping Type | Source Field (Microsoft Dynamics NAV) | Destination Field (iPaaS.com) | Description |
Field |
| Cost | Recommended. Inventory cost. |
Field |
| 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 |
| QtyAvailable | Recommended. Quantity available. |
Field |
| 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
Capture a variant whose parent product already exists in iPaaS.com; confirm the variant and its inventory appear correctly linked to the parent.
Update a variant's price or inventory in NAV and re-run; confirm the iPaaS.com variant and inventory update without duplicating.
Confirm inventory lands at the location configured in Default iPaaS Location Id For Inventory.
Validation Checklist
The Items web service is published in NAV with the exact service name
Items.Parent products exist in iPaaS.com before variants are captured.
The Default iPaaS Location Id For Inventory points at a captured iPaaS.com location.
Additional Notes
Base products are captured separately through the Product To iPaaS.com collections.
For directionality, required web services, and environment-specific behaviors, see the Microsoft Dynamics NAV Known Limitations article.