Multi-language support lets product design teams define part name and description translations in an external PLM system, then flow them into D365 F&SCM alongside the standard product data.
The integration exposes the translated data on a Translations tab and stores it centrally in the Released products data model, keeping localized product metadata consistent across legal entities and processes such as customer documents, e-commerce feeds, EDI messages, and reports.
This document covers the concepts behind multi-language support, then the tasks to configure, use, and maintain product translations.
What multi-language support provides
Multi-language support delivers localized part name and part description values from an external PLM system into D365 F&SCM. Product design teams define the translations in the PLM system using standardized ISO language codes. The integration structures the translations in the import file and processes them when you post the staging journal.
The feature provides the following capabilities:
The integration propagates localized part names and descriptions from the PLM system to D365 F&SCM.
The system centralizes translations so that every product lifecycle stage uses consistent multilingual data.
The translation data is exposed through a dedicated data entity, so it can also be extended to other multilingual scenarios, such as product catalogs or regulatory labeling, through standard Data management workspace and OData integration.
Note
This feature applies only to translations on the released product and product variant. It does not apply to translations on other entities, such as BOM line descriptions or route operation texts.
The Translations tab
The Translations tab is the primary place where you review multilingual data. The integration displays the tab in two locations:
On the Staging journal line details screen, so that a Master Data Manager can review translations imported for a part.
On the Engineering change order (ECO) details screen, so that an Engineering Change Manager can review translations during change impact assessments and engineering approvals.
The Translations tab presents a grid with the following columns:
Language code - the ISO language code for the translation.
Translated part name - the part name in the translated language.
Translated part description - the part description in the translated language.
The Translations tab in the ECO details screen is always visible, regardless of whether a staging journal is linked. This gives you a consistent view of multilingual product information across all ECOs.
Note
If the PLM source delivers a language code that is not enabled in Organization administration > Languages, or that is not a valid ISO language code, the system skips that translation and logs a warning in the staging journal Infolog. It does not stop processing of the rest of the import.
The product translations table
When you post a staging journal or an ECO, the system validates the translations and writes them to a central product translations table within the Released products data model. The table stores one record per part number and language code. Because the data is exposed through a dedicated data entity, you can import, export, and integrate the translation data through the Data management workspace, OData, and other integration channels. To locate the entity, search the Data management workspace entity list for "product translation."
Import scenarios
The integration processes translations consistently across all PLM import scenarios. Translation behavior does not vary by scenario, only the surrounding import context differs:
Import Part - imports product and translation data for parts.
Import ECO - imports engineering change orders together with translation data.
Import Migration - imports product data during a data migration.
Import Release - imports product data during a release.
Translation update strategy
When you re-import product data for a part that already exists in Dynamics 365 F&SCM, the Translation update strategy parameter controls how the integration applies the translation updates. The parameter provides two modes:
Variant-only updates (default) - the integration applies translation updates only to the product variants. The main product translations remain unchanged. This mode preserves the behavior of earlier versions.
Product and variant updates - the integration applies translation updates to both the main product and all of its related product variants, keeping them synchronized with the PLM source.
Use this parameter to prevent translation drift between a main product and its variants. Without synchronization, the main product and its variants can display different names in customer-facing documents, e-commerce feeds, EDI messages, and reports.
Note
After you upgrade, the Translation update strategy parameter defaults to Variant-only updates. Your existing behavior does not change until you explicitly select Product and variant updates.
Prerequisites
Complete the following prerequisites before you configure and use multi-language support:
Install and configure STAEDEAN PLM Integration for D365 F&SCM.
Define at least one PLM system in Engineering change management > PLM integration > PLM systems.
Enable the required languages in Organization administration > Languages.
Confirm with your PLM administrator which ISO language codes the source system will send, so you can enable the matching languages in D365 F&SCM.
Ensure that products created earlier through the PLM Integration exist in D365 F&SCM, so that you can test re-imports.
Confirm that you have the PLM Integration Administrator role, or an equivalent security role.