Error messages

When you use Tinx Connector, errors can appear in different places, such as webshop orders or job queue log entries. This article contains the most common errors listed alphabetically. Each error includes an explanation of what caused it and how to fix it. For step-by-step instructions or more details, follow the links to the related articles.

If something isn’t syncing and you’re not sure what the error is, start with the Troubleshooting checklist. After you identify the issue, return to this section to find the solution, if necessary.

Blocked must be equal to ‘No’ in Item: No.={item_number}. Current value is ‘Yes’

This error occurs when you try to create a sales order in Business Central and one of the items on the order is marked as blocked. For more information, see Block items. Tinx Connector checks the Blocked field on the Item card before creating a sales order based on a webshop order. If you accept the sale of the item, you must unblock it first. For more information, see To block an item.

Item {webshop_sku_number} doesn’t exist in database

This error occurs when a webshop order contains a product that is not matched to any item in Business Central. Tinx Connector cannot create a sales order for this product. The order is imported into the Webshop Orders page with the Blocked Order field set to Yes.

1. Create a new item in Business Central with the same item number as the webshop SKU.
2. Open the order lines of the blocked webshop order, and clear the Item Blocked checkbox for the affected lines.

For more information, see Orders with products not matched with items in Business Central.

The activity was deadlocked with another user who was modifying…

This error occurs when another user or process, such as a job queue, interferes with the processes Tinx Connector is trying to execute. For example, a stock report in Tinx Connector might take 30 minutes to run. If another user manually modifies the same table during that time, the two processes will conflict. Similarly, if another job queue tries to run for the same table while Tinx Connector is processing that table, you get this error.

If this error happens frequently, you need to identify the conflicting processes and reschedule them so they don’t interfere with each other. You can do this by analyzing the telemetry data in Business Central. You can ask a Business Central partner to analyze the telemetry data.

The data does not represent a valid JSON token

This error occurs when Tinx Connector receives a webshop response that cannot be interpreted as valid JSON. There are many possible causes. Some common examples include:

• Connection or network issue: Tinx Connector cannot establish a connection with the webshop, for example: 502 Bad Gateway error. Resolve the problem on the webshop side.
• Incorrect API endpoint: The API endpoint configured in Tinx Connector does not point to the correct location, causing the server to return an unexpected, non-JSON response.
• Invalid response from the webshop: A plugin or custom module on the webshop returns plain text instead of JSON.

Because the cause can vary, there’s no single solution. Review the Web Response on the Synchronisation Ledger Entries page to understand what the webshop actually returned and to identify the cause. For more information, see View and Download on Synchronisation Ledger Entries page.

The field Sell-to Customer No. of table Sales Header contains a value ({customer_number}) that cannot be found in the related table (Customer)

There are two common reasons for this error:

• The Webshop Customers page, which allows Tinx Connector to match the webshop customer to the Business Central customer, contains an incorrect Business Central customer number. For example, the webshop customer is linked to a Business Central customer that was deleted. In that case, update the matching to link the webshop customer to an existing Business Central customer. For more information, see Customer and item matching.
• The Sell-to Customer No. mapping in the message definition that is related to sales order creation contains a hardcoded Customer No. value that doesn’t exist in Business Central. This applies to messages such as WOO-087 in WooCommerce, M2R-087 in Magento, and GQL-124 in Shopify. In such a case, you need to update the mapping to reference a valid Business Central customer.

For more information, see Item & Customer Matching and Customers.

The field Shipping Agent Service Code of table Sales Header contains a value ({value})

The shipping agent service code from the webshop is either missing in Business Central or is not mapped to a corresponding code. When Tinx Connector attempts to create a sales order, Business Central validates the shipping agent service code. If the code is invalid or missing, Business Central rejects the order. Companies typically manage shipping methods on the webshop side. This error occurs when you add a new shipping method in the webshop but haven’t updated the corresponding code in Business Central.

Ensure that the shipping agent service exists in Business Central or create it. Then map it to the webshop shipping agent. You can map the shipping methods in two places:

• The Conversion List page.
• The Web Shipment Method page.

The supplied field number ‘{field_number}’ cannot be found in the ‘{table_name}’ table

This error indicates that a specific field number cannot be found in a specific table. A customization or extension in Business Central might have removed or altered the field referenced in the error message. If you no longer need the field, delete the field mapping. Or, if the field is still needed, restore it in Business Central.

The value “{value}” cannot be evaluated into type Integer

Tinx Connector attempts to enter a value in a field that only accepts whole numbers within a specific range (Integer). For example, after publishing a product to Shopify, you receive a GID value, such as gid://shopify/Product/1234567890. If Tinx Connector tries to enter this value into the field that accepts only integers, you get this error message. Another example is when the numeric value is too large for the Integer type. For more information, see Integer data type.

Follow these steps to resolve the issue.

1. Select Search (Alt+Q) in the upper-right corner, enter Synchronisation Ledger Entries, and then choose the related link.
2. Select the entry with the error, and then on the action bar, in the Download group, select the Web Response action.
3. Review the Web Response to see the fields that Tinx Connector uses and the values they contain.
4. On the Synchronisation Ledger Entries page, choose Entry, and then choose Message Definition to open the message for that entry.
5. On the Message Definition page, on the Lines FastTab, choose the Fields action to see the list of fields mapped in that message.
6. On the Message Line Field page, locate the field that corresponds to the problematic value from the web response and correct the mapping so that the field returns a valid integer value.

You cannot create this type of document when Customer ({customer_number}) is blocked

You receive this error when you attempt to create a sales order in Business Central and the customer is marked as blocked. Tinx Connector checks the Blocked field on the Customer card before creating a sales order based on a webshop order. You must unblock the customer before accepting the sale. As with blocked items, before unblocking the customer, make sure you understand the business reasons for the block.

Related information

Troubleshooting checklist
Advanced troubleshooting
Synchronization ledger entries
Customer and item matching
Synchronize orders
Key concepts in Tinx Connector