General
Web Text Blob Fields
Added some extra web text blob fields (i.e. Web Text Custom 1 (33, BLOB) etc.) to our TINX Web Text Header (11205295) table, allowing for custom texts to be synced between systems.
New field for Item by Sales Channel
A new field, Activation Date (Date), has been added to table TINX Item by Sales Channel (11205331) to
track when an item becomes active. If the Activation Date field is empty when an item is published, the system will now automatically populate it with today’s date.
Amazon
Amazon Bulk Shipment
The shipment message logic has been updated to support bulk shipping. This allows for sending multiple fulfillments in a single Feed API request to Amazon. In order to do this, a new field, "No. of Requests per Job", has been added to the Message Definition. Currently, this is set to send one request per job execution to avoid "Quota Exceeded" errors. This value can be adjusted based on the Feed API Quota in the future.
The bulk shipping message uses the same structure as the single shipment message. Only minor field adjustments are required to convert it to bulk shipping format. See below.
Magento
Multiple Message Line Conditions
It is now possible to use multiple conditions with the TINX Message Line Conditions (11205312) feature, including support for multiple options within a single field using the comma (,) sign and the IN operator.
In the example below this means that a default value is given if Custom Field 1 = bundle and either Custom Field 2 is 59 or 46. Therefore in this case there are two scenarios in which the conditions can be matched.
Shopify
Order Lines Linking
When using multiple sales channels, the Calcfield No. of Order Lines in the TINX Webshop Order was previously linked only to the Entity ID. This has now been updated to also link to the Increment ID, ensuring that the order lines are accurately associated with a specific order from a specific sales channel, eliminating the risk of mixed data.
Standardized Image Height
We've introduced a new feature in Report 11205780 - Copy Default Images: Image Resize Height. When running the report, the connector populates the TINX Image - Video Link (11205284) table with copies of product images stored in BC (one per item). With this new setting, users can define the height of an image before it is added to the table, while the width is automatically adjusted to maintain the correct aspect ratio. This functionality is particularly useful for clients selling products like alcohol, where images often showcase bottles of varying shapes and sizes.
To use this, first head to Setup > Feature Management. There, enable the line called 'Feature: Enable resizing image during copy from Item to "Image - Video Link" with report "Copy Image to Image link'.
Next, head to the E-commerce Setup page and you fill in the height (in pixels) you'd like to use in a newly added field, Image Resize Height.
WooCommerce
Empty Values in products/%1/variations Endpoint
Resolved an issue where requests based on the products/%1/variations endpoint were sending default values for certain fields, even though these were not being mapped.
Order Event Functionality (Cancel Order)
We’ve added a new feature to our connector: Outbound Events. This feature allows us to build custom events that are semi-customizable, enabling unique flows of information tailored to specific business needs. These events function similarly to the existing Order Events, where a process is triggered with additional code to support the desired functionality.
The first event we’ve introduced is called: 'Sales Order On After Confirm Post (Manually).'
How It Works:
-
Scenario
- When a customer places an order in WooCommerce, Tinx imports the order into BC.
- If the customer later cancels the order and the sales order is manually deleted in BC, this new event ensures synchronization with WooCommerce.
-
Workflow
- Upon posting the sales order in BC (manually), Tinx triggers a popup with a question such as: "Update WooCommerce order status to Cancelled?".
- This popup appears only for relevant online orders imported via the connector. The text can be changed.
-
Action
- If the user confirms, Tinx sends a PUT request to the WooCommerce API endpoint /wp-json/wc/v3/orders/<id>, updating the order status in WooCommerce to "Cancelled."
- This ensures the order statuses in BC and WooCommerce remain synchronized, avoiding discrepancies between platforms.
This first event demonstrates the flexibility and potential of the Outbound Events feature, paving the way for more advanced, tailored integrations in the future.
Outbound Order meta_data
The connector now supports sending meta_data for messages targeting the order endpoint (orders/%1), enabling custom information to be included in WooCommerce updates.
Example: when updating an order to completed, you can include meta_data such as a Track & Trace URL
{"status": "completed",
"meta_data": [
{"key": "track_and_trace",
"value": "https://tastyparent.nl/121212231"}]}
This adds flexibility for custom updates like shipment tracking.
Formatting Decimal Values Issue
Previously, in the WooCommerce codeunit, a formatting issue occurred when values were added to the JSON tag. If a format expression was also applied in the message field, it could lead to invalid data formatting due to regional settings.
Example of the Issue:
- Unit Price = 3,12
- After applying the message field format → 3.12 (as WooCommerce expects).
- After JSON formatting (Dutch region) → 312 (incorrect).