General
New Multi-Channel Tables
We have added new tables to the Tinx app for multi-channel purposes:
- TINX Customer by Sales Channel (11205332)
- TINX Contact by Sales Channel (11205918)
- TINX Ship Address Sales Channel (11205358)
- TINX B2B Pricing Sales Channel (11205359)
These tables are designed for storing IDs per sales channel. The first two can be found in a new E-Commerce tab on the Customer card (18) and Contact card (5050).
When using shipping addresses per sales channel or B2B pricing, new boolean values must be checked on the Sales Channel Card.
Customer Template Lookup via Shipping Country
When using the connector to create customer cards for web customers, you can use BC Customer Templates. There are various criteria for doing so (e.g., based on the country, region, or sales channel). By default, the connector filters for the Billing Country when searching for the correct template. A recent feature allows you to search using the Shipping Country instead.
This is particularly useful when the shipping country or information needs to be updated for each new order placed by a customer already existing in BC.
To set this up:
- Check the box 'Customer Template Search on Shipping Country' on the Sales Channel card.
- In the mapping of the customer create message (usually the XXX-008 message), add the required fields.
This will result in the TINX Shipping Country (11205275) field being filled in on the customer card, and the correct template being used.
New Order Event
We've added a new order event to our connector: Create Whse. Receipt. When using the codeunit 11205756 TINX Order Function Mgt. after creating a sales return order, this will automatically create a Warehouse Receipt for the order.
Order Event Conditions
It is now possible to add filters when using order events. For example, a client might configure the connector so that after a sales order is created, the document is released, and an assembly order is created.
You can now determine the criteria under which these order events should occur, such as only for certain locations or specific IDs.
Synchronization Dashboard Job Edit
We've added a button to the Synchronization Dashboard for the Job Queue Entry table. This allows you to more quickly turn specific jobs, such as the TINX NAS Inbound Mgt. codeunit, on or off.
Image Extension Web
It is now possible to use WebP as a source for images in our TINX Image - Video Link (11205284) table. This means we currently support WebP, JPEG, PNG, and GIF formats.
Amazon
Automation of Amazon Product Import Report
The report used to download products from the Amazon Seller API into the Tinx Webshop Product table is now automated.
Magento
Magento Connection via OAuth
It is now possible to use OAuth when linking a Magento backend with BC. To obtain the credentials from Magento, go to System > Integrations and click edit on the relevant record (e.g., Tinx or Webshop). The Access Token and Access Token Secret are required.
In this case, all four fields are needed in the connector, with the latter two being those used for OAuth 1.0.
Comma Fix for Custom Attributes (SOAP)
For one of our clients, we noticed that a custom attribute was not accepted by Magento due to a formatting issue.
Example request:
<![CDATA[ warehouse-center,distributor,engine-dealer,equipment-dealer,installation-partner,webshop,e-drive-dealer, ] ]>
The issue was caused by the last comma after 'e-drive-dealer'. This has been fixed.
Shopify
GraphQL and an Integer Parser
As Shopify gradually phases out the REST API, various endpoints related to the Shopify Plus connector can now only be accessed via GraphQL. For example, data about companies is now obtained through this method.
For the connector, we have already set up various mappings. A new one is for downloading a list of Shopify customers via GraphQL into our Tinx Webshop Customer table.
Since GraphQL mutations and queries often involve GID values in addition to regular ID values, we've added a new button to our field mapping tables: Parse GID. When checked, the connector will parse a GID value and extract the Integer value at the end. For instance, Shopify might return a value of 'gid://shopify/Customer/7364011524308' for the ID, which is then stored as '7364011524308' in our table.
Attribute Formula for Customer and Product Metafields
When using a formula for a value in our Tinx Attribute setup, such as a metafield, the connector now rounds down numbers for integer and decimal values. For example, a quantity of 1,700 will now be sent as 1700. This adjustment applies to both Customer and Product attributes.
Shopware
Custom Field Array
It is now possible to send a custom field value to Shopware as an array.
{
"customFields": {
"article_conditions": [
{
"article_class": "AFG_GESAMT",
"condition_percent": 20,
"state": "freigegeben"
},
{
"article_class": "WEIN",
"condition_percent": 15,
"state": "freigegeben"
},
{
"article_class": "AFG-GASTRO",
"condition_percent": 15,
"state": "nicht freigegeben"
}
]
}
}
Addition of customFields to Addresses
It is now possible to send custom fields in the address section for Shopware.
{"addresses": [
{
"city": "Stuhr",
"phoneNumber": "0421 561733",
"street": "Zeppelin Str.",
"zipcode": "288161",
"countryId": "c129e7e7b2cf46eda98d24ddb4cc9ad5",
"id": "f96b2fc87d32a7dfa07089b4becb72c8",
"lastName": "Alker",
"firstName": "Ommen GmbH",
"company": "Alker + Ommen GmbH",
"customFields": {
"sitegeist_customer_address_housenumber": "15"}}
The value you need is added directly in the mapping.
WooCommerce
Customer Update Message
When sending product updates to WooCommerce, specifically regarding the meta_data section, empty billing and shipping values were being sent along with the request, resulting in rejected messages by WooCommerce. This has been fixed.