Before you start this section, complete the Troubleshooting checklist and review the list of Error messages.
The following steps require a high level of permissions and in-depth knowledge of Tinx Connector. In some cases, the changes made during these steps can cause unintended issues. Use these solutions only if you’re an advanced user. Otherwise, contact the Tinx Support Team.
Ensure your Tinx Connector is up to date
If you use Business Central on-premises, ensure you use the latest version of Tinx Connector. Contact the Tinx Support Team to get the latest version of the app.
Regenerate your webshop keys
You might experience synchronization issues when moving from a test to a live environment or when setting up a new environment.
Generate and enter new keys for your webshop. This process is different for each webshop. For more information, see Connect with your webshop and select the instructions for your webshop.
Check the triggers
Check the trigger of the message definition, such as OnModify or OnInsert. For delete actions, On Modify is often preferred. Ensure you use the correct trigger. This applies only to outbound messages.
Use Postman
Use Postman to check rejected outgoing messages. The webshop’s response shows the expected message format. Reviewing this response is more efficient than making trial-and-error changes in Business Central. With Postman, you can adjust the message to ensure it is accepted.
Postman can also help diagnose issues with the Dynamics 365 Business Central on-premises version. If an API call works from Postman but not from the on-premises BC server, that tells you the issue is likely whitelisting on the on-premises server.
Postman is an external tool that you can use to send API requests. You can use Postman to test the same API calls that Business Central makes to your webshop. For more information, see Postman documentation.
Check the mappings
Mappings are the most complex element to check when troubleshooting, and changes to mappings have the most impact. They should be the last thing you check and modify. To identify which mapping might be causing an error, see Step 2: Check the webshop order fault reasons. In some cases, you might know the mappings are causing the problem, but you might not be sure which mapping. You can select Ignore Field on the Message Line Field page and apply that setting to one or two lines at a time. Check whether this resolves the error to narrow down the list of potential problematic mappings.
For more information, see Default Mapping.
Related information
Troubleshooting
checklist
Error messages
Synchronization ledger
entries
Job queues
Key concepts in Tinx
Connector