Summary

iPaaS.com product variants can be transferred into Microsoft Dynamics NAV through the Variant From iPaaS.com mapping collections. Microsoft Dynamics NAV has no native variant concept, so each variant is written as its own flat item on the Items endpoint — the Add collection creates a new item and the Update collection refreshes an existing one.

ID Format

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

Pattern: the iPaaS.com variant SKU
Example: 1000-RED-L

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 variant to its NAV item.

Deleted Record Support

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

Custom Field Support

Custom fields are not supported for this collection type in this direction.

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 Variant Add and Variant Update From iPaaS.com collections both target the same Microsoft Dynamics NAV item. The Product From iPaaS.com collections also write to the NAV Items endpoint, so product and variant transfers share the same item table — keep iPaaS.com product 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 variants; 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.

Supported Child Collections

None for the write to NAV. (Variant inventory flows in the opposite direction — see the Product Variant 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 variants cannot transfer.
Fixed configuration values must be valid in your NAV company. Variants are created with Costing Method AVERAGE, Gen. Prod. Posting Group FINISHED, Inventory Posting Group FINISHED (Update collection), Tax Group Code TAXABLE, and Order Tracking Policy Tracking Only. The posting group and tax group codes (FINISHED, TAXABLE) are instance-specific and must already exist in the target NAV company, or NAV rejects the item — change these mappings to values valid in your environment.
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. Validate field requirements in a staging environment before relying on them in production.

iPaaS.com Caveats

The variant 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 variant 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 with the fixed costing method, posting groups, tax group, and tracking policy.
The Microsoft Dynamics NAV item number (No.) is retained as the external ID for future updates.

Mappings

Add/Update Microsoft Dynamics NAV Product Variant FROM iPaaS.com

iPaaS.com data type: Product Variant

Description. Writes the iPaaS.com variant to a Microsoft Dynamics NAV item. The Add and Update collections share the same field mappings; Update additionally sets the Inventory Posting Group and 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/identifies the NAV item number; the unique key used to link and update the item.
Field	`Weight`	Net_Weight	Recommended. Item net weight.
Dynamic Formula	`return "AVERAGE";`	Costing_Method	Recommended. Fixed Costing Method; must be a valid NAV costing method.
Dynamic Formula	`return "FINISHED";`	Gen_Prod_Posting_Group	Recommended. Fixed Gen. Prod. Posting Group; instance-specific code that must exist in the target NAV company.
Dynamic Formula	`return "FINISHED";`	Inventory_Posting_Group	Recommended. (Update collection only) Fixed Inventory Posting Group; instance-specific code that must exist in NAV.
Dynamic Formula	`return "TAXABLE";`	Tax_Group_Code	Recommended. Fixed Tax Group Code; instance-specific code that must exist in NAV.
Static	`"Tracking Only"`	Order_Tracking_Policy	Recommended. Fixed Order Tracking Policy; must be a valid NAV Order Tracking Policy.

Error Handling

For the catalog of subscriber-visible errors, see the Microsoft Dynamics NAV Error Messages article. NAV rejects a variant write when a required field is missing or when the posting group, tax group, costing method, or tracking policy value does not exist in the target company.

Testing & Validation

Test Scenarios

Create a new variant in iPaaS.com and run the Add transfer; confirm a NAV item is created with the expected number, weight, and the configured posting/tax groups.
Update a field on an existing variant and run the Update transfer; confirm the change appears in NAV and that unmapped fields are preserved.
Attempt a transfer when the configured posting group or tax group code does not exist in NAV; confirm NAV returns a clear validation error.
Run a manual sync using the variant 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 configured Costing Method, Gen. Prod. Posting Group, Inventory Posting Group, Tax Group Code, and Order Tracking Policy all exist in the target NAV company.

Additional Notes

Products are written to the same NAV Items endpoint through the separate Product From iPaaS.com collections.
For directionality, required web services, value-replacement (including the FINISHED/TAXABLE codes), and environment-specific behaviors, see the Microsoft Dynamics NAV Known Limitations article.

iPaaS.com to Microsoft Dynamics NAV Product Variant Mapping Documentation