Overview
This article catalogs the error messages a subscriber may encounter when synchronizing data between iPaaS.com and Microsoft Dynamics NAV, grouped by transfer flow. Each entry explains what causes the error and how to resolve it. Errors raised by Microsoft Dynamics NAV itself (for example, a rejected record) are shown as the integration surfaces them; configuration and validation errors raised by the integration can usually be resolved by the subscriber.
For integration behaviors that do not produce an error (directionality, fixed values, read-only entities), see the Microsoft Dynamics NAV Known Limitations article; for per-field behavior, see the relevant Mapping Documentation article.
Supported Flows
Customer and Company From iPaaS.com
Sales Order From iPaaS.com
Product and Variant From iPaaS.com
Customer and Company From iPaaS.com
Duplicate-matching prefix missing
"CustomerNumber Duplicate Prefix preset is null/empty while CommaSeparated Customer CustomField Matching Name & Value preset has this value: \<value>"
Description: The CommaSeparated Customer CustomField Matching Name & Value setting is configured, but the CustomerNumber Duplicate Prefix setting is empty. The two settings work together for duplicate matching and must both be set.
Resolution: In the subscription settings, set the CustomerNumber Duplicate Prefix, or clear the CommaSeparated Customer CustomField Matching Name & Value setting if prefix-based matching is not needed. See the Connections and Settings article.
Duplicate-matching value is misformatted
"CommaSeparated Customer CustomField Matching Name & Value preset (\<value>) has badly formatted data. The correct format is: customFieldName,customFieldValue"
Description: The CommaSeparated Customer CustomField Matching Name & Value setting is not a single
name,valuepair separated by one comma.Resolution: Re-enter the setting as
customFieldName,customFieldValue(for example,Active,yes). See the Connections and Settings article.
Customer or company rejected by Microsoft Dynamics NAV
"Could not create the customer in Microsoft Dynamics NAV." (or the equivalent update message)
Description: Microsoft Dynamics NAV rejected the customer/company write. This usually means a field required by your NAV configuration was not provided, or a referenced value (such as a posting group) does not exist in the target company. Microsoft Dynamics NAV's own validation message is included with the error when available.
Resolution: Review the NAV validation detail, confirm the required fields are mapped, and ensure referenced codes exist in NAV. Validate in a staging environment. If the message does not indicate a configuration cause, contact iPaaS.com Product Support for assistance.
Sales Order From iPaaS.com
Customer has no posting group
"This transaction cannot be created because the customer does not have a posting group. Please resolve this issue manually."
Description: The transfer filter requires the order's linked customer (or company) to have a Customer Posting Group in Microsoft Dynamics NAV. The linked customer does not have one.
Resolution: Assign a Customer Posting Group to the customer in Microsoft Dynamics NAV, then retry the transfer.
No linked customer or company
"Please provide either a valid 'companyId' or 'customerId'."
Description: The transaction is in a state to transfer, but it has neither a linked iPaaS.com customer nor a linked company to resolve the NAV Sell-to Customer.
Resolution: Ensure the transaction's customer or company is linked between iPaaS.com and Microsoft Dynamics NAV before transferring.
A line item could not be saved
"An error occurred saving a line item (Descr: \<line description>). The order was created in Microsoft Dynamics NAV but is not complete."
Description: The sales order header was created in Microsoft Dynamics NAV, but one of its line items could not be saved (for example, the item does not exist in NAV or a line field was rejected). The order remains incomplete.
Resolution: Review the named line, confirm the item and its line fields are valid in Microsoft Dynamics NAV, and retry. The order header already exists, so the retry completes the remaining lines.
Product and Variant From iPaaS.com
Product or variant rejected by Microsoft Dynamics NAV
"Could not create the product in Microsoft Dynamics NAV." (or the equivalent update message)
Description: Microsoft Dynamics NAV rejected the item write. Common causes are a referenced Tax Group Code, Posting Group, Costing Method, or Order Tracking Policy value that does not exist in the target company, or a field required by your NAV configuration that was not mapped. (Variants are written as flat NAV items with fixed posting/tax-group values — see the Product Variant From iPaaS.com mapping documentation.)
Resolution: Confirm the referenced codes exist in Microsoft Dynamics NAV and that required item fields are mapped; replace the example posting/tax-group values with codes valid in your environment. Validate in a staging environment. If the cause is not a configuration value, contact iPaaS.com Product Support for assistance.