New or changed features in Release 10.0.44.19 (July 2025) - PLM integration for Engineering Change Management.

1. Multi Language Support for PLM Integration

The PLM Integration framework now supports multi-language capabilities for managing product data across different languages and regions. This enhancement enables organizations to maintain product information in multiple languages while preserving data integrity and synchronization with PLM systems.

1.1 Key Benefits:

• Maintain consistent product information across all global markets by centralizing translation management within the PLM system, ensuring that all regions receive the same accurate product data
• Manage translations directly in PLM systems, eliminating manual processes and reducing the risk of errors that occur when product information is translated separately in each market
• Ensure synchronized updates across all language variants when product information changes, so that modifications to product specifications automatically cascade to all translated versions
• Provide customer-facing teams with accurate, localized product information automatically through the integration, improving customer communication and reducing time spent on manual translation lookups
• Reduce duplicate translation efforts across different regional teams by maintaining a single source of truth for multilingual product data in the PLM system

1.2 Feature Overview

Multi Language Support provides comprehensive translation capabilities for engineering product data transferred between PLM systems and Dynamics 365 Finance & Operations.

1.3 Key Capabilities

1.3.1 Translations Tab on Staging Journal Line Details

New functionality includes:

• A dedicated Translations tab has been added to both the Staging Journal Line Details screen and the Engineering Change Order interface, providing a unified location to view and validate multilingual product information imported from PLM systems
• The tab displays a structured grid showing
  • Language code (following ISO standards)
  • Translated part name
  • Translated part description
  for each configured language, making it easy to review all language variants at a glance
• Master Data Managers and Engineering Change Managers can use this interface to validate multilingual content before posting, ensuring accuracy across all languages and catching any translation issues early in the process

Example: When reviewing part number MOTOR-AX500, users can see translations in English ("High-performance electric motor"), German ("Hochleistungs-Elektromotor"), and French ("Moteur électrique haute performance"), with each translation displaying the appropriate localized names and descriptions for the target market.

1.3.2 Translation Processing During Staging Journal Posting for Import Parts Scenario

Import Part scenario enhancements:

• The system automatically processes and validates all translation entries during the staging journal posting process, checking that language codes exist in the Dynamics 365 Language Table configuration and ensuring data integrity
• Intelligent duplicate detection identifies when translations for the same product and language combination already exist, automatically updating the existing records rather than creating duplicates that could cause confusion
• Comprehensive error logging captures detailed information about any validation failures, including unsupported language codes or missing required fields, providing clear guidance for data correction

Processing behavior:

• Successfully validated translations are persisted to the Product Translations table, making them immediately available throughout Dynamics 365 Finance & Operations for use in sales orders, documentation, and customer communications
• When the system encounters invalid entries, such as unsupported language codes or incomplete translation data, these problematic records are skipped without blocking the entire journal posting process, ensuring business continuity
• A detailed processing log captures all skipped entries with specific error messages, allowing administrators to review issues and take corrective action without disrupting the main import flow
• The system's ability to handle partial translation issues means that valid translations are processed successfully even when some records contain errors, preventing a few problematic entries from blocking an entire batch

1.3.3 Engineering Change Order Translation Management

• The Translations tab is seamlessly integrated within the ECO details screen, ensuring that multilingual product data remains accessible and manageable throughout the entire change management process
• When staging journals with Import ECO type are posted, translation data automatically populates the ECO's Translations tab, eliminating manual data entry and ensuring consistency between the staging data and the change order
• The consistent display format across both staging journal and ECO interfaces reduces the learning curve for users, as they see the same familiar grid structure with language codes, translated names, and descriptions regardless of where they access the data
• Engineering teams can effectively review multilingual content during change impact assessments, ensuring that product changes are properly communicated across all languages and markets before approval

1.3.4 Translation Persistence Through ECO Posting

• During ECO posting, the system automatically updates the Released Product Translations table with any new or modified translation data for all items affected by the change order, ensuring that approved changes flow through to the final product records
• Translation data flows seamlessly to all products impacted by the engineering change, whether they are new items being introduced or existing products being modified, maintaining consistency across the entire product portfolio
• The system maintains perfect consistency between products imported directly through the Import Parts scenario and those processed through formal engineering change procedures, ensuring uniform translation handling regardless of the import method
• Full lifecycle support ensures that multilingual product information remains synchronized from initial import through engineering changes to final release across all legal entities, providing end-to-end translation management