Skip to main content

Microsoft Dynamics NAV Error Messages

Common Microsoft Dynamics NAV integration errors on iPaaS.com, what causes them, and how to resolve each.

Overview

This article catalogs the errors the Microsoft Dynamics NAV integration can record in the iPaaS.com error logs, grouped by transfer flow. Each error carries a stable code you can search for on this page (for example, MNAV-EXTN-1001), the message as it appears, what causes it, and how to resolve it. To find an error you saw in the Dashboard > Integration Monitoring > Error Logs, copy its code and use your browser's find (Ctrl+F or Cmd+F) to jump to it here.

Some resolutions refer to your Managed Integration Service Provider (MiSP) — the partner who set up and maintains your integration (your mappings, connection settings and credentials, and data reconciliation). If a resolution is beyond what you can change yourself, your MiSP is the first point of contact.

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.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Supported Flows

  • Connection and Settings

  • Customer From iPaaS.com

  • Company From iPaaS.com

  • Product From iPaaS.com

  • Product Inventory To iPaaS.com

  • Location To iPaaS.com

  • Shipping Method To iPaaS.com

  • Invoice To iPaaS.com

  • Sales Order From iPaaS.com

Error Collection

Connection and Settings

Connection could not be established

MNAV-AUTH-1001 - {connection validation detail}

  • Description: The integration could not establish a connection to Microsoft Dynamics NAV. The specific reason returned by the connection check is included with the error — most often invalid or expired NAV credentials, an unreachable OData service URL, or a NAV user that is not authorized.

  • Resolution: Confirm the NAV OData API URL, company, environment, and credentials in the subscription settings are current and that the NAV user is active and authorized. See the Connections and Settings article. If the settings are correct and the connection still fails, contact your MiSP.

Invalid Poll Time UTC Adjustment setting

MNAV-VALD-1004 - The Poll Time UTC Adjustment setting has an invalid value: {value}. Enter a valid numeric hour offset.

  • Description: The Poll Time UTC Adjustment subscription setting is not a valid numeric hour offset, so the integration cannot adjust the polling window.

  • Resolution: Set Poll Time UTC Adjustment to a valid numeric hour offset (for example, -5) in the subscription settings. See the Connections and Settings article.

Customer From iPaaS.com

Duplicate-matching prefix missing

MNAV-VALD-1001 - 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

MNAV-VALD-1002 - 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,value pair separated by one comma.

  • Resolution: Re-enter the setting as customFieldName,customFieldValue (for example, Active,yes). See the Connections and Settings article.

Unable to link existing customer

MNAV-BIZL-1005 - Unable to dynamically link to the existing iPaaS.com customer using email address. This may result in duplicate customer records.

  • Description: A customer with the same email address already exists in iPaaS.com, but the integration was unable to link the incoming customer to it. A duplicate customer record may be created.

  • Resolution: This is a warning; the transfer can still complete. Check for duplicate customers with the same email address in iPaaS.com and, if found, have your MiSP reconcile (merge or link) them. Confirming the email address is consistent between systems prevents a recurrence.

Customer rejected by Microsoft Dynamics NAV (create)

MNAV-EXTN-1001 - Could not create the customer in Microsoft Dynamics NAV.

  • Description: Microsoft Dynamics NAV rejected the customer create. 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. NAV's own validation message is included with the error when available.

  • Resolution: Review the NAV validation detail included with the error, confirm the required fields are mapped, and ensure referenced codes exist in NAV. Validate the change in a staging environment before retrying in production.

Customer rejected by Microsoft Dynamics NAV (update)

MNAV-EXTN-1002 - Could not update the customer in Microsoft Dynamics NAV.

  • Description: Microsoft Dynamics NAV rejected the customer update — typically a required field was cleared, or a referenced value does not exist in the target company.

  • Resolution: Review the NAV validation detail, confirm the mapped fields and referenced codes are valid in NAV, and retry. Validate in a staging environment first.

Company From iPaaS.com

Company's linked customer not found

MNAV-NFND-1006 - Could not find the customer for this company in Microsoft Dynamics NAV.

  • Description: The integration writes a company to NAV as a Customer record, but the NAV customer that the company should resolve to could not be found.

  • Resolution: Confirm the company is linked between iPaaS.com and NAV, and that its NAV customer record still exists. If the link is missing, have your MiSP re-establish it, then retry the transfer.

Company rejected by Microsoft Dynamics NAV (create)

MNAV-EXTN-1003 - Could not create the company in Microsoft Dynamics NAV.

  • Description: Microsoft Dynamics NAV rejected the company write (companies are written as NAV Customer records). A required field was likely not provided, or a referenced value such as a posting group does not exist in the target company.

  • Resolution: Review the NAV validation detail, confirm required fields are mapped, and ensure referenced codes exist in NAV. Validate in a staging environment before retrying.

Company rejected by Microsoft Dynamics NAV (update)

MNAV-EXTN-1004 - Could not update the company in Microsoft Dynamics NAV.

  • Description: Microsoft Dynamics NAV rejected the company update — typically a required field was cleared or a referenced value does not exist in the target company.

  • Resolution: Review the NAV validation detail, confirm the mapped fields and referenced codes are valid, and retry after validating in a staging environment.

Product From iPaaS.com

Product not found

MNAV-NFND-1001 - Could not find the product in Microsoft Dynamics NAV.

  • Description: The integration attempted to read a product from NAV that could not be found — for example, the referenced item no longer exists in the target company.

  • Resolution: Confirm the item exists in Microsoft Dynamics NAV and that the product is linked between the two systems. If the item was removed in NAV, remove or remap the corresponding iPaaS.com product.

Unable to link existing product

MNAV-BIZL-1001 - Unable to dynamically link to the existing iPaaS.com product using Product No. This may result in duplicate product records.

  • Description: A product with the same Product No. already exists in iPaaS.com, but the integration was unable to link the incoming product to it. A duplicate product record may be created.

  • Resolution: This is a warning; the transfer can still complete. Check for duplicate products with the same Product No. in iPaaS.com and, if found, have your MiSP reconcile them.

Unable to link existing product inventory

MNAV-BIZL-1002 - Unable to dynamically link to the existing iPaaS.com product inventory using Product and Location Id. This may result in duplicate product inventory records.

  • Description: A product-inventory record for the same product and location already exists in iPaaS.com, but the integration was unable to link the incoming inventory to it. A duplicate inventory record may be created.

  • Resolution: This is a warning; the transfer can still complete. Confirm the Default iPaaS Location Id For Inventory setting is correct and check for duplicate inventory records for the product and location. Have your MiSP reconcile any duplicates.

Unable to link existing product by SKU

MNAV-BIZL-1006 - Unable to dynamically link to the existing iPaaS.com product using SKU. This may result in duplicate product records.

  • Description: A product with the same SKU already exists in iPaaS.com, but the integration was unable to link the incoming product to it. A duplicate product record may be created.

  • Resolution: This is a warning; the transfer can still complete. Check for duplicate products with the same SKU in iPaaS.com and, if found, have your MiSP reconcile them.

Product rejected by Microsoft Dynamics NAV (create)

MNAV-EXTN-1005 - Could not create the product in Microsoft Dynamics NAV.

  • 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 any example posting/tax-group values with codes valid in your environment. Validate in a staging environment before retrying.

Product rejected by Microsoft Dynamics NAV (update)

MNAV-EXTN-1006 - Could not update the product in Microsoft Dynamics NAV.

  • Description: Microsoft Dynamics NAV rejected the item update — typically a referenced code does not exist in the target company or a required field was cleared.

  • Resolution: Confirm the referenced codes and required item fields are valid in NAV, and retry after validating in a staging environment.

Product prerequisite could not be created

MNAV-EXTN-1011 - Unable to create the product. This will prevent the transfer of the product.

  • Description: Before completing the transfer, the integration tried to create a prerequisite product in NAV and the create failed, so the overall transfer cannot proceed.

  • Resolution: Look for the accompanying product create error (for example, MNAV-EXTN-1005) in the same error log entry and resolve that underlying cause, then retry.

Product Inventory To iPaaS.com

Product for inventory not found

MNAV-NFND-1002 - Could not find the product for this inventory in Microsoft Dynamics NAV.

  • Description: A standalone product-inventory transfer referenced a product that could not be found in NAV, so its inventory cannot be captured.

  • Resolution: Confirm the product exists in Microsoft Dynamics NAV and is linked to iPaaS.com before the inventory record can transfer. If the item was removed in NAV, remove or remap the corresponding iPaaS.com product.

Location To iPaaS.com

Location not found

MNAV-NFND-1003 - Could not find the location in Microsoft Dynamics NAV by this id: {id}.

  • Description: The integration attempted to read a location from NAV by id and it could not be found.

  • Resolution: Confirm the location still exists in Microsoft Dynamics NAV. If it was removed, remove or remap the corresponding iPaaS.com location.

Unable to link existing location

MNAV-BIZL-1003 - Unable to dynamically link to the existing iPaaS.com location using name. This may result in duplicate location records.

  • Description: A location with the same name already exists in iPaaS.com, but the integration was unable to link the captured location to it. A duplicate location record may be created.

  • Resolution: This is a warning; the transfer can still complete. Check for duplicate locations with the same name in iPaaS.com and, if found, have your MiSP reconcile them.

Shipping Method To iPaaS.com

Shipping method not found

MNAV-NFND-1004 - Could not find the shipping method in Microsoft Dynamics NAV.

  • Description: The integration attempted to read a shipping method (NAV Shipping Agent) that could not be found.

  • Resolution: Confirm the shipping agent still exists in Microsoft Dynamics NAV. If it was removed, remove or remap the corresponding iPaaS.com shipping method.

Unable to link existing shipping method

MNAV-BIZL-1004 - Unable to dynamically link to the existing iPaaS.com shipping method using name. This may result in duplicate shipping method records.

  • Description: A shipping method with the same name already exists in iPaaS.com, but the integration was unable to link the captured shipping method to it. A duplicate record may be created.

  • Resolution: This is a warning; the transfer can still complete. Check for duplicate shipping methods with the same name in iPaaS.com and, if found, have your MiSP reconcile them.

Invoice To iPaaS.com

Invoice not found

MNAV-NFND-1007 - Could not find the invoice in Microsoft Dynamics NAV by this id: {id}.

  • Description: The integration attempted to read a posted sales invoice from NAV by its order number and none was found (for example, the invoice has not been posted yet, or the referenced order no longer exists in the target company).

  • Resolution: Confirm the sales invoice is posted in Microsoft Dynamics NAV and that its order number matches the record being transferred. If the invoice was removed in NAV, remove or remap the corresponding iPaaS.com record.

Invalid collision match field

MNAV-BIZL-1011 - Invalid collision match field: {fieldMatch}.

  • Description: The invoice mapping collection's collision configuration specifies a match field the integration does not support for invoices.

  • Resolution: Have your MiSP review the invoice mapping collection's collision configuration and set it to a supported match field. See the Connections and Settings article for the Collision Handling Method options.

Sales Order From iPaaS.com

No linked customer or company

MNAV-VALD-1003 - Please provide either a valid 'companyId' or 'customerId'.

  • Description: The transaction is ready 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.

Customer has no posting group

MNAV-BIZL-1010 - This transaction cannot be created because the customer does not have a posting group. Please resolve this issue manually.

  • Description: The transfer 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.

Sales order not found

MNAV-NFND-1005 - Could not find the sales order in Microsoft Dynamics NAV.

  • Description: The integration attempted to read a sales order from NAV that could not be found — for example, the referenced order no longer exists in the target company.

  • Resolution: Confirm the order exists in Microsoft Dynamics NAV and is linked to iPaaS.com. If it was removed in NAV, remove or remap the corresponding iPaaS.com transaction.

Unable to link existing sales order

MNAV-BIZL-1007 - Unable to dynamically link to the existing Microsoft Dynamics NAV sales order using Transaction Number. This may result in duplicate transaction records.

  • Description: A sales order with the same Transaction Number already exists, but the integration was unable to link the incoming order to it. A duplicate transaction record may be created.

  • Resolution: This is a warning; the transfer can still complete. Check for duplicate transactions with the same Transaction Number and, if found, have your MiSP reconcile them.

Unable to link existing sales order line

MNAV-BIZL-1008 - Unable to dynamically link to the existing Microsoft Dynamics NAV sales order line using Transaction Number. This may result in duplicate transaction line records.

  • Description: A sales order line for the same Transaction Number already exists, but the integration was unable to link the incoming line to it. A duplicate transaction line record may be created.

  • Resolution: This is a warning; the transfer can still complete. Check for duplicate transaction lines and, if found, have your MiSP reconcile them.

Invalid collision match field

MNAV-BIZL-1009 - Invalid collision match field: {fieldMatch}.

  • Description: The mapping collection's collision configuration specifies a match field the integration does not support for sales orders.

  • Resolution: Have your MiSP review the sales order mapping collection's collision configuration and set it to a supported match field. See the Connections and Settings article for the Collision Handling Method options.

A line item could not be saved

MNAV-EXTN-1007 - An error occurred saving a line item (Descr: {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.

Sales order lines could not be created

MNAV-EXTN-1016 - Sales order lines could not be created in Microsoft Dynamics NAV.

  • Description: The integration could not write the order's line items to Microsoft Dynamics NAV. This is the underlying line-creation failure that a "line item could not be saved" error (MNAV-EXTN-1007) reports at the order level.

  • Resolution: Confirm the ordered items exist in Microsoft Dynamics NAV and that each line's fields are valid, then retry. If a specific line is named in the accompanying MNAV-EXTN-1007 entry, start there.

Order could not be marked complete

MNAV-EXTN-1008 - An error occurred marking the order to complete. The order was created in Microsoft Dynamics NAV but is not complete.

  • Description: The order and its lines were created, but the final step that marks the order complete in NAV failed. The order remains flagged as incomplete.

  • Resolution: Review the NAV detail included with the error, confirm the completion field configured for your environment is valid, and retry. The order already exists, so the retry re-attempts only the completion step.

Unexpected response creating sales order

MNAV-EXTN-1009 - The sales order create returned an unexpected response from Microsoft Dynamics NAV.

  • Description: The sales order create call to NAV returned a response the integration could not interpret as a successful order.

  • Resolution: Retry the transfer. If it recurs, review the NAV detail included with the error and confirm the order's required fields and referenced codes are valid; if the response remains unexpected, contact your MiSP to review with iPaaS.com Support.

Unexpected response updating sales order

MNAV-EXTN-1010 - The sales order update returned an unexpected response from Microsoft Dynamics NAV.

  • Description: The sales order update call to NAV returned a response the integration could not interpret as a successful update.

  • Resolution: Retry the transfer. If it recurs, review the NAV detail included with the error and confirm the mapped fields are valid; if the response remains unexpected, contact your MiSP to review with iPaaS.com Support.

Customer prerequisite could not be created

MNAV-EXTN-1012 - Unable to create the customer. This will prevent the transfer of the sales order.

  • Description: Before writing the order, the integration tried to create the order's prerequisite customer in NAV and the create failed, so the order cannot transfer.

  • Resolution: Look for the accompanying customer create error (for example, MNAV-EXTN-1001) in the same error log entry and resolve that underlying cause, then retry.

Company prerequisite could not be created

MNAV-EXTN-1013 - Unable to create the company. This will prevent the transfer of the sales order.

  • Description: Before writing the order, the integration tried to create the order's prerequisite company in NAV and the create failed, so the order cannot transfer.

  • Resolution: Look for the accompanying company create error (for example, MNAV-EXTN-1003) in the same error log entry and resolve that underlying cause, then retry.

Product prerequisite could not be created (order line)

MNAV-EXTN-1014 - Unable to create the product (SKU: {sku}). This will prevent the transfer of the order.

  • Description: Before writing the order, the integration tried to create a prerequisite product for one of the order lines and the create failed, so the order cannot transfer.

  • Resolution: Look for the accompanying product create error (for example, MNAV-EXTN-1005) for the named SKU in the same error log entry and resolve that underlying cause, then retry.

All Flows

Microsoft Dynamics NAV API call failed

MNAV-EXTN-1015 - Error calling Microsoft Dynamics NAV.

  • Description: A call to the Microsoft Dynamics NAV OData API failed or returned an error. The integration includes the NAV response (or the transport error) with this code. This is the catch-all for a NAV-side call failure that is not covered by a more specific code above, and it can occur on any flow.

  • Resolution: Review the NAV response included with the error. A transient failure (a timeout, a temporary lock) usually succeeds on the next scheduled sync. If it persists, confirm the NAV OData service is reachable and the connection credentials are current in the subscription settings; if the NAV response indicates a data problem, correct the referenced record. If you cannot resolve it from the NAV detail, contact your MiSP.

Batch call to Microsoft Dynamics NAV failed

MNAV-EXTN-1017 - An error occurred during a batch call to Microsoft Dynamics NAV. {first underlying error}

  • Description: The integration sends some Microsoft Dynamics NAV operations in batches; one of the calls in a batch failed and the underlying error is included with this code. This can occur on any flow that writes multiple related records together (for example, a sales order and its lines).

  • Resolution: Review the underlying error included with the message and resolve it (it often carries its own code, such as MNAV-EXTN-1015 or a line-level error), then retry the transfer.

Related Documents

Related Articles
Did this answer your question?