Common Issues and Solutions

When using the Tinx connector you may run into issues when trying to send or update data between systems. Some common issues are listed below with advice on how to fix them.

 

Messages Are Not Triggered

If you check the 'Publish to Webshop' box for an item and cannot find it in the Record Queue, but the underlying messages (XX-020 for example) are enabled, please check the following.

Steps:

  1. Review the filters applied to the message. It could be that because of filters, no record is added to the queue.
  2. Check the trigger of the message (e.g. OnModify or OnInsert). For delete actions, On Modify is often preferred. Is the correct trigger in use?
  3. Close the client and log in again. (In the case of Navision, sign out and back in). This sometimes resolves issues when publishing attributes.
  4. Check if the 'Analysis/Debug Mode + Development Mode + Enable Change Log' are enabled in E-commerce Integration Setup. Most often only the 'Enable Change Log' setting is required.
  5. Use Postman to check outgoing messages that are rejected. See how the webshop wants to receive the messages (via the repsonse) instead of modifying and pushing changes in BC.

 

Inbound Process Has Stopped

When the inbound process stops, it's often because BC cannot create something with the available data, such as a sales order or customer card. For customer card creation, ensure the customer pricing group and VAT groups, etc. are filled in for customers with ID 0 or empty ('') values.

For orders, if there is no value in the Default Customer field, then perhaps a filter is missing on the XX-087 message: Default Customer No. <> ''.

No. Series in Mapping Not Working Properly

Sometimes a customer is not created correctly or gets an incorrect number series. This can be due to improper setup, mapping issues, or validation problems.

Solution:

  1. Remove the mapping rule and re-add it.

  2. Select the desired no. series during re-adding. This sometimes resolves the issue.

 

No Valid Gen. Bus. Posting Group for Customer No. = ‘’

During the creation of orders via the XX-087 message, an error about a missing Gen. Bus. Posting Group for Customer No. = ‘’ (empty) can occur. This can mean that the customer card wasn't created correctly and does not show in the Webshop Order table, which is used to get this field (i.e. the Default Customer No., field 73). 

Steps:

  1. Identify the path the connector is trying to follow via mapping in XX-087.
  2. Go to the webshop order and check the data using "About This Page."
  3. Verify that Default Customer No. (field 73 in Tinx Webshop Order table) is empty, but NAV Customer No. (field 95) is filled.
  4. Navigate to the order and check Webshop Customer No. > Advanced to confirm the customer card is not created.

 

WooCommerce: Fetch Specific Orders After Date

Use the web service for WooCommerce and Shopify to fetch specific orders by date, including pagination and order sorting.

 

Filters Not Working Properly / All in Lowercase

If filters are in lowercase, it means you haven't specified which table to use for the filters.

Solution: indicate the Info Table No. (which table) and Field No. (often Item No.) on the Card of the message you want to filter.



Error Messages and Fixes

Error: The data does not represent a valid JSON token.

  • Cause: Whitelisting issue.
  • Solution: Whitelist the IP of BC on the webshop. If unsure, have the webshop partner monitor while making live calls.

Error: "{"errors":[{"status":"403","code":"FRAMEWORK__MISSING_PRIVILEGE_ERROR","title":"Forbidden","detail":"{ u0022message u0022: u0022Missing privilege u0022, u0022missingPrivileges u0022:[ u0022product_price
u0022]}","meta":{"parameters":[]}}]}"

  • Cause: API role is not administrator in Shopware.
  • Solution: Change the API role in the integration to administrator.

 

Error: The type NavInteger is unknown.

  • Cause: Usually a mapping issue. The connector is trying to get a value from a field for which the type doesn't mach.
  • Solution: Find the field in question and change the field type (e.g., from Code to Text or BigInteger to Code).\

 

Error: The filter "=XXX" is not valid for timestamp field on the Webshop Orders table. The value (XXX but can be any number of filtes) can't be evaluated into type BigInteger.

  • Cause: Message filters set incorrectly. This often happens when a message is copied and the filters are copied as well.
  • Solution: Remove and re-add the filters for the message. Be sure to check the message Card to see if the table and link are correct for the table you wish to filter on. I.e. for the XX-087 message we use filters of table 11205270.

 

Error: The record is not open.

  • Cause: Often an attribute issue.
  • Solution: Check the linking of values for attributes on the card, either in the message for attributes or the attribute card itself.