This article describes the known limitations, fixed behaviors, and configuration prerequisites of the iPaaS.com Microsoft Dynamics NAV integration. Review it alongside the mapping collection documentation before enabling transfers in production.

Areas covered: Directionality · Update behavior · Required web services · Sales orders · Customers & companies · Products, variants & inventory · Tracking · Values to replace before go-live · Environment-specific behaviors

Directionality

Each entity flows in a fixed direction; the integration does not reverse these:

Written to Microsoft Dynamics NAV (from iPaaS.com): Customers, Companies, Products, Product Variants, Sales Orders (and their lines).
Captured into iPaaS.com (from Microsoft Dynamics NAV): Locations, Shipping Methods, Product Inventory, Sales Orders/Transactions, Sales Invoices, and shipment tracking numbers.
Read-only in Microsoft Dynamics NAV: Locations, Shipping Methods, Product Inventory, and Sales Invoices are only captured into iPaaS.com; the integration does not create or update them in NAV.
Company capture (NAV → iPaaS.com) is not available in this version. Companies are written from iPaaS.com to NAV only; there is no scheduled capture of companies from NAV into iPaaS.com.

Update Behavior

Updates written to Microsoft Dynamics NAV are applied as a partial merge: a field is changed only when the mapping produces a non-empty value. Empty or unmapped source values never blank out existing NAV data. To clear a value in NAV, change it directly in NAV rather than expecting an empty source value to overwrite it.

Required Web Services

Transfers depend on the corresponding OData web services being published in Microsoft Dynamics NAV (under Web Services), each with its exact service name:

Customers — customers and companies
Items — products, variants, and product inventory
SalesOrders — sales orders / transactions and their addresses, payments, and tracking
SalesOrderLines — sales order line items
SalesInvoices — posted invoices (required for invoice transfers; confirm it is published even if it does not appear in older installation instructions)
Locations — locations
ShippingAgents — shipping methods

If a required web service is not published, the related records cannot transfer.

Field Requirements

Microsoft Dynamics NAV does not publish its field requirements in a public API specification, and required fields vary by company configuration. Before relying on a transfer in production, review the relevant NAV card (customer, item, sales order) for fields marked as required and confirm each is mapped. An unmapped required field causes NAV to reject the record. Validate field requirements in a staging environment first.

Sales Orders

Capture into iPaaS.com is limited to valid orders. A sales order is captured only when its NAV status is Released and its Sell-to Customer is linked to an existing iPaaS.com customer or company. Orders that do not meet both conditions are skipped.
Writing to NAV is limited to Pending transactions with a posting group. A transaction is written to NAV only when its status is Pending and its linked customer (or company) resolves to a NAV customer that has a Customer Posting Group. If the customer has no posting group, or no customer/company is linked, the transfer stops with an error.
Order totals come from the first line's running totals. The transaction Subtotal and Total are read from the order's line totals (excluding/including VAT); the total quantity sums only Item-type lines.
Only item lines transfer as line items. Sales order and invoice line collections transfer only lines whose type is Item; shipping, tax, and G/L-account lines are not captured as standard line items.

Customers and Companies

Companies are written as NAV customer records. Both the Customer and Company collections write to the NAV Customers endpoint; a company is represented as a customer record in NAV.
Duplicate-matching presets must be configured together. If the subscription setting CommaSeparated Customer CustomField Matching Name & Value is set, the CustomerNumber Duplicate Prefix setting must also be set, or customer transfers fail. The matching setting must be a single customFieldName,customFieldValue pair. See the Customer mapping documentation for details.
The customer name maps from the first name only. As shipped, the NAV customer Name is populated from the iPaaS.com customer First Name; adjust the mapping if a full or company name is required.

Products, Variants, and Inventory

Variants are flat items in NAV. Microsoft Dynamics NAV has no native product-to-variant relationship, so each variant is created as its own NAV item. When capturing variants into iPaaS.com, the parent-product relationship is resolved from iPaaS.com.
Captured product/variant name is the item number. When products and variants are captured into iPaaS.com, the 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. Product and variant inventory is recorded against the iPaaS.com location given by the Default iPaaS Location Id For Inventory subscription setting; if that setting is empty, a valid iPaaS.com location id must be supplied on the LocationId mapping, or the inventory cannot be placed.
Inventory's parent product must exist in iPaaS.com. Standalone inventory links to its parent product; if the product has not been transferred, the inventory cannot link.

Tracking

Shipment tracking is captured only for item lines that have a package tracking number; lines without a tracking number are excluded. Tracking detail is assembled from several NAV shipment records (the order line, sales shipment, and shipment line).

Values to Replace Before Go-Live

Some mappings ship with fixed example or instance-specific values that must be reviewed and replaced for your environment:

Variant posting and tax groups. New variants are created with Gen. Prod. Posting Group FINISHED, Inventory Posting Group FINISHED, and Tax Group Code TAXABLE. These codes must exist in your NAV company; replace them with codes valid in your environment.
G/L-account SKUs on sales order lines. Sales order lines with SKU 24400 or 24102 are written as G/L Account lines; these are example SKUs. Replace them with the SKUs your environment uses for G/L-account lines, or remove the special case.
Country/Region Code fallback. When a billing or shipping address has no country, the country code falls back to US. Confirm this is appropriate if you serve customers outside the United States.
Costing method and order tracking policy. New items use Costing Method AVERAGE and Order Tracking Policy Tracking Only; confirm these match your NAV item configuration.

Environment-Specific Behaviors

NAV API UTC filtering quirk. Microsoft Dynamics NAV evaluates date filters against the server's local time even though the underlying data is stored in UTC, which can produce unexpected polling results. The Poll Time UTC Adjustment subscription setting compensates for this; set it if polling misses or duplicates recently changed records.
Polling windows are configurable. Transaction, Product, and Product Inventory polling each have their own search-day and (where applicable) page-size and date-field-override settings. See the Connections and Settings documentation.

Microsoft Dynamics NAV Known Limitations