DocumentsCorePack (DCP) provides multilingual support, allowing users to generate documents in their preferred language. This article explores the different translation options in DocumentsCorePack and how users can customize language settings for a seamless experience. Seamlessly integrated with Microsoft Dynamics 365, DCP ensures automatic language adaptation, maintaining consistency. Whether you need to set a specific language for a template or modify dialog text for localization, this guide will walk you through the essential steps to optimize multilingual support in DocumentsCorePack.
Table of Contents
- Setting Template Specific Languages
- Product Translations in Templates
- Customizing Dialog Texts
- Localization of the Template Designer
Setting Template Specific Languages
By default, DCP generates documents in the language specified by the user’s language setting that runs the document process. However, there are scenarios where a different language is required for specific templates, such as always using German translations in documents for German-speaking clients, irrespective of the user’s default language.
- For more details, read How to set a specific language in your template.
Product Translations in Templates
Microsoft Dynamics 365 enables the translation of product attributes, including names and descriptions. This feature ensures that product details align with the recipient’s language.
- For more details, read How to use product translations in DocumentsCorePack templates.
Customizing Dialog Texts
To enhance user experience, DocumentsCorePack allows localization of the DocumentsCorePack Dialog for Dynamics 365 and model-driven apps. Users can customize the text in DocumentsCorePack dialogs by modifying the DocumentsCorePack Dialog Localization XML file. They can also add custom translation nodes for various languages, ensuring the dialog text is displayed in the preferred language.
- For more details, read Learn how to create custom translations.
Localization of the Template Designer
The Word-based designer supports localization through XML files named after the language code (e.g., en.xml, de.xml). Five languages are available out of the box. Still, customers can create custom translations by copying an existing file, translating the elements, and saving it with the appropriate language code (e.g., fr.xml). The system automatically detects the language based on the user’s selection in Dynamics 365 and applies the corresponding translation.
By implementing these configurations, organizations can ensure that DCP aligns with their multilingual requirements, delivering a seamless and localized document generation experience.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.