Translator Product Catalog Localization

Overview

This flow maintains a multilingual product catalog using Microsoft Translator V3, Dataverse, and Excel Online (Business). On a daily schedule it reads product records from Dataverse, applies a brand/SKU glossary (Translator dynamic-dictionary markup) to protect names and codes, translates the name/description/spec fields into each configured target locale, writes the localized values back into a dedicated Dataverse table, and appends each localized row to a per-locale Excel catalog for regional storefronts. Manually localizing catalogs is slow and error-prone, and brand terms get mangled by raw machine translation; glossary-aware translation keeps every locale current while protecting brand names and SKUs.

Use Case

An e-commerce / marketing team sells in multiple regions and needs product content localized consistently, refreshed on a schedule, with per-locale exports it can hand to regional storefront owners. The team curates source product copy in English (in Dataverse) plus a small glossary of brand/SKU terms that must never be translated.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Translator	shared_microsofttranslatorv	Translate
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Excel Online (Business)	shared_excelonlinebusiness	AddRowV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Add locales

Append codes to flowlibs_TargetLocales (e.g. fr,de,es,it,ja); the locale loop scales automatically.

Selective re-translate

The $filter skips products already marked Localized; clear flowlibs_localizationstatus to re-localize, or extend the filter to a Pending model.

Review queue

Write localized rows with a Draft status and add an Approvals step before marking the master Localized.

Storefront push

Replace the Excel AddRowV2 export with a commerce connector (Shopify, etc.) writing localized fields directly.

Glossary scope

Use flowlibs_targetlocale on glossary rows to apply locale-specific protected translations (filter the glossary ListRecords per locale).

On-change trigger

Swap the Recurrence trigger for a Dataverse SubscribeWebhookTrigger on the product table to localize on edit instead of on schedule.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@replace(variables('varMarkedName'), items('Apply_To_Each_Glossary_Term')?['flowlibs_name'], concat('<mstrans:dictionary translation="', coalesce(items('Apply_To_Each_Glossary_Term')?['flowlibs_protectedtranslation'], items('Apply_To_Each_Glossary_Term')?['flowlibs_name']), '">', items('Apply_To_Each_Glossary_Term')?['flowlibs_name'], '</mstrans:dictionary>'))

[ { "Text": "@{variables('varMarkedName')}" } ]

@first(body('Translate_Name'))?['TranslatedText']

@concat(coalesce(items('Apply_To_Each_Product')?['flowlibs_sku'], items('Apply_To_Each_Product')?['flowlibs_name']), ' | ', items('Apply_To_Each_Locale'))

Customize & download