This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2024 Wave 2.
The 19th of the new functionality in the Application section is synchronize product translations to Shopify.
Automatically synchronizing translations from Business Central to Shopify guarantees consistent product descriptions and details across various languages. Offering customers product information in their native language enhances accessibility and satisfaction, which can boost conversion rates and foster customer loyalty.
Enabled for: Users by admins, makers, or analysts
Public Preview: –
General Availability: Oct 2024
Feature Details
To include translations to the product synchronization, follow these steps:
- Choose the Tell Me icon, enter Shopify shops, and choose the related link.
- Select the shop to open the Shopify Shop Card page.
- To open the Shopify Languages page, choose the Languages action.
- To import languages enabled on Shopify, choose the Refresh action. Notice that the primary language isn’t be listed. For the primary language, continue to use the Language Code field in the Shopify Shop Card.
- For each language you want to include ino synchronization, fill in the Language Code field and turn on the Sync translations toggle.
That’s it. Translations are included every time you run the Sync Product task either manually or by using the job queue.
More information
- A new Shopify permission (scope) is needed: read_locales. You must request a new access token.
- The first export of items, initiated by the Add item to Shopify action, doesn’t include translations. You need to run Sync product and turn on the Can Update Shopify Products toggle.
- Marketing text is only added for the primary language.
- Extended texts are added for each language, plus extended texts where the All Languages toggle is turned on.
- Attributes are added for each language. If a translation is missing, the primary language is used.
- Item translations are added for each language if a translation is defined.
- Variant translations aren’t used because the connector only exports the variant code, and not its description.
Extensibility impact
The CreateProductBody procedure in the Product Export codeunit takes language codes as parameters so it can be used for each language. Now this procedure is called multiple times according to the list of selected languages. Because it contains the OnBeforeCreateProductBodyHtml and OnAfterCreateProductBodyHtml events, those events are now triggered multiple times per item. The events now include the language code as a parameter, so you can skip translation or add your own logic.