Overview
This document provides a comprehensive overview of error messages that may occur within the Microsoft Dynamics 365 Business Central integration. Each error entry includes the error title, the actual error message, a description of the trigger condition, and the recommended resolution.
Supported Flows
Add/Update Business Central Sales Order FROM iPaaS.com
Add/Update Business Central Sales Invoice FROM iPaaS.com
Add/Update Business Central Payment FROM iPaaS.com
Add/Update Business Central Journal Line FROM iPaaS.com
Note that error resolution for other flows may be added at a later date.
Error Collection
Add/Update Business Central Sales Order FROM iPaaS.com
Duplicate Transaction Risk
Unable to dynamically link to existing Dynamic Sales Order using Transaction Number. This may result in duplicate Transaction records.
Description: This error occurs when the integration attempts to link an iPaaS.com transaction to an existing sales order in Business Central using the transaction number, but the dynamic linking fails. This typically happens when the external ID creation response does not match the expected sales order ID, or the system cannot correctly associate the transaction with an existing record.
Resolution: Verify that the sales order exists in Business Central and that the transaction number is correctly mapped. Check that the external ID mapping is functioning properly and that no duplicate transaction numbers exist in the source system. If the issue persists, contact iPaaS.com Product Support for assistance.
Customer Creation Failed
Unable to create customer. This will prevent the transfer of the sales order.
Description: This error occurs when the integration attempts to create or sync a customer from iPaaS.com to Business Central as a prerequisite for the sales order, but the customer creation process fails. This may be caused by missing required fields, validation errors, or API failures during customer creation.
Resolution: Verify that the customer record in iPaaS.com contains all required fields (name, email, address). Check that the Business Central API endpoint is functioning correctly and review any validation error messages returned by the API. Retry the transaction after correcting the customer data.
Company Creation Failed
Unable to create company. This will prevent the transfer of the sales order.
Description: This error occurs when the integration attempts to create or sync a company (customer company) record from iPaaS.com to Business Central, but the operation fails. This may be caused by missing required fields, invalid data, or API errors.
Resolution: Verify the company data in iPaaS.com, ensure all required fields are populated, and confirm that the Business Central API is responding correctly. Retry the transaction after correcting the company data. If the issue persists, contact iPaaS.com Product Support for assistance.
Duplicate Transaction Line Risk
Unable to dynamically link to existing Dynamic Sales Order Line using Transaction Number. This may result in duplicate Transaction Line records.
Description: This error occurs when the integration attempts to link a transaction line from iPaaS.com to an existing sales order line in Business Central, but the dynamic linking fails. This typically happens when the external ID response does not match the expected order line ID, or the system cannot uniquely identify the correct line item.
Resolution: Verify that the sales order lines exist in Business Central and that SKUs and quantities match correctly. Check that the external ID mapping is functioning properly. If the issue persists, contact iPaaS.com Product Support for assistance.
Product Creation Failed
Unable to create product sku: {orderLine.Sku}. This will prevent the transfer of the order.
Description: This error occurs when the integration attempts to create a product in Business Central because it does not exist (but is on a line item on the order), but the product creation process fails. This may happen due to missing required fields, invalid SKU data, or API errors.
Resolution: Verify that the product exists in iPaaS.com with a valid SKU and that all required product fields are populated. Check that the Business Central product API is functioning correctly. Retry the transaction after correcting the product data.
Add/Update Business Central Sales Invoice FROM iPaaS.com
Invalid Tax Code or G/L Account
Invalid tax code or G/L account number is supplied
Description: This error occurs when Business Central rejects an invalid or non-existent tax code or G/L account number passed from iPaaS.com. The value does not match any configured records in Business Central.
Resolution: Verify that tax code and G/L account mappings between iPaaS.com and Business Central are aligned. Update any static values to valid accounts. In Business Central, confirm that the provided tax codes and G/L account numbers exist and are active.
Missing Inventory Account
Inventory Account is missing in Inventory Posting Setup Location Code: {LocationCode}, Invt. Posting Group Code: {PostingGroup}
Description: This error occurs when Business Central cannot find an Inventory Account configured in Inventory Posting Setup for the given Location Code and Posting Group, preventing inventory-related postings.
Resolution: In Business Central, navigate to Inventory Posting Setup and configure a valid Inventory Account for the specified Location Code and Posting Group combination. Ensure the item is assigned to the correct Inventory Posting Group, then retry the transaction from iPaaS.com.
Invalid LocationId Type
Cannot convert the literal ‘MAIN’ to the expected type ‘Edm.Guid’. (locationId)
Description: This error occurs when the Business Central API expects a GUID for locationId but receives a string value like “MAIN”, causing a type mismatch.
Resolution: Update the mapping logic to convert location codes to their corresponding GUIDs before sending to Business Central. Verify the correct GUID for each location in Business Central via the API or the Locations page. Contact iPaaS.com Product Support if the mapping collection needs to be updated.
Missing Customer Posting Group
Customer Posting Group must have a value in Customer: No.={CustomerNo}
Description: This error occurs when the customer record used in the transaction does not have a required Customer Posting Group assigned, which prevents Business Central from completing financial postings.
Resolution: In Business Central, open the customer record and assign a valid Customer Posting Group. Retry the transaction from iPaaS.com after the posting group is configured.
Unbalanced G/L Entry
Balance must be equal to ‘0’ in G/L Account: No.={AccountNo}
Description: This error occurs when a financial transaction is not balanced (debits do not equal credits), which Business Central requires for all postings.
Resolution: Review the transaction to ensure that all debit and credit amounts balance. Verify posting setups including Customer Posting Group and General Posting Setup. Correct any missing or incorrect account mappings. If the issue persists, contact iPaaS.com Product Support for assistance.
Invalid OData Filter
The filter “”=‘SELLACRE24_W%2FOORINGS’”” is not valid for the No. field on the Item table
Description: This error occurs when an OData filter contains invalid syntax or disallowed characters for the field, causing Business Central to reject the query. URL-encoded characters (e.g., %2F for /) in item numbers may not be properly handled.
Resolution: Verify that the item number in iPaaS.com does not contain special characters that conflict with OData filter syntax. If the item number contains forward slashes or other special characters, ensure they are properly encoded. Contact iPaaS.com Product Support if the filter logic needs to be corrected.
Add/Update Business Central Payment FROM iPaaS.com
Customer Ledger Entry Not Found
There is no Cust. Ledger Entry within the filter
Description: This error occurs when no Customer Ledger Entry matches the provided filter criteria in Business Central, so the payment cannot be applied or reconciled.
Resolution: Verify that the filter values (customer number, document number, amount) match an existing open entry in Business Central. Ensure the invoice is posted and still open (not already applied). Adjust the mapping logic if the references are incorrect.
Invalid Payment Amount Sign
The “amount” should be a negative number
Description: This error occurs when a payment amount is sent as a positive value but Business Central expects a negative value for payment or receipt entries.
Resolution: Update the mapping logic to send negative values where Business Central requires them. Verify that upstream systems are not already sending negative values that would be double-negated. Contact iPaaS.com Product Support if the mapping collection formula needs to be updated.
Add/Update Business Central Journal Line FROM iPaaS.com
Missing Journal Identification
You must specify a journal batch ID or a journal ID to get a journal line
Description: This error occurs when a journal line is created or retrieved without specifying a journalId or journalBatchId, so Business Central cannot determine which journal to use.
Resolution: Verify that the journal exists in Business Central and that the JournalId field is properly mapped and populated in the mapping collection. The integration uses GetCustomerPaymentJournalIdByNameAsync to resolve journal IDs by name. Contact iPaaS.com Product Support if the journal mapping needs to be configured.
Invalid Account Reference
The field Account No. of table Gen. Journal Line contains a value ({AccountNo}) that cannot be found in the related table ({TableName})
Description: This error occurs when a journal line references an account number that does not exist in the related table (e.g., Vendor, Customer, G/L Account), causing validation failure in Business Central.
Resolution: Verify that the referenced account number exists in the correct table in Business Central. Update the mapping or source data in iPaaS.com to use a valid account number. Ensure that master data between iPaaS.com and Business Central is consistent.