This release includes key improvements across connectors and core functionality. Highlights include enhanced GraphQL parameter handling, improved Amazon product import with better character support, lot number support for Shopify sales invoices, and optimized WooCommerce product requests. We've also added new custom fields for pricing calculations and expanded copy item functionality with attribute support.

General

Ignore Request Parameters

Fixed an issue where for GraphQL configuration (say for a given Query), ignoring set request parameters was not working. When ignored, they are now ignored. Similarly, we fixed an issue where general message line filters being ignored were not working properly.

BC Attribute ID Flowfield

Added two new flowfields in the TINX Attribute Options (11205761) and TINX Attribute Options V2 (11205917) tables. These get their values from the field BC Attribute ID (100, BigInteger) and BC Attribute Name (102, Text[250]) from table TINX Attribute (11205755).

Blob Field Filtering

It is now possible to filter on a Blob field with a value different than empty. Before this fix, the value was always kept in the payload. Example below, where a message line is checking whether a description is filled in or not.

Product Variant Length Error Fix

Fixed an issue where when changing the no. of a product with variants, an error popped up stating that the length was too long for the Variant Code field.

Enhanced Copy Item Function

Extended the default Copy Item (page 729) report with new functionality. Now a new boolean field 'Copy Attributes' is added, allowing one to copy all default BC attributes as well when copying an item.

Purchase Document Entity ID Support

Similar to sales orders and invoices, we've added the Tinx Entity ID (11025251, BigInteger) to purchase orders, posted purchase receipts and posted purchase invoices that follow the creation of a sales document via the Tinx connector. Note that just like with sales orders, if the document was not made by the connector, these fields are obviously not filled in.

Amazon

Product Import Character Handling

Fixed an issue when using the Amazon Product Import report (11205846) with data from Amazon (i.e. 'GET_MERCHANT_LISTINGS_ALL_DATA') to copy item data into table 11205274. Some characters were not accepted, such as '('. Even if some items have these characters, the report should still run. This has been fixed.

Additional Custom Fields

Added some additional custom text (2048 characters) and custom decimal fields to the table TINX Amazon Sales Order Line (11205341), allowing for more use of formulas and calculations with pricing for clients.

MplusKASSA

Negative Paid Amount Field

To facilitate the posting of outstanding invoices, a negative amount is often needed for the General Journal Line. This field is now added in the Tinx POS Receipt Header table (11205810).

Shopify

Category Assignment Queue Enhancement

Fixed an issue where when running report 11205808, the connector would not add records to the queue for category - item links, if the underlying table had already been filled (but did not yet have a Webshop Value ID). Now this does happen and based on the filters of the SHOP-080 message and event triggers on other messages, such as SHOP-020, you can trigger the message more or less as per your choosing.
To set this up, please go to the Web Category page and select Setup, under Home. There, check the box 'Add to records queue if item already published'.

Lot Numbers for Sales Invoices

Extended one of our Order Posting Events: Assign Lotnumbers. Now when this is set up, the connector doesn't just add lot numbers to sales orders, but also sales invoices, if that is chosen as the sales document of creation via the mapping.

WooCommerce

Optimized Product Variations Request

Removed certain fields from the default request to WooCommerce for products, such as an empty 'attributes' array, stock settings and description. Now this is only sent if it's actively used in the mapping.

Sales Channel Transfer Enhancement

Currently, when matching BC customers with webshop customers, the "Publish to Webshop" field in the BC customer card is used. Now we also transfer the Sales Channel value to table 18 to the field TINX Sales Channel (11205272, Code[20]). This can be useful in situations when clients differ in B2C and B2B customers and work with report 11205320 (Create Customer Card per Sales Channel from Guest Order).