Master Data Language Translation
Introduction
Master data translation feature makes your work processes seamless across languages. You can add translations in D365 for key terms like lifecycle states, work order types, job types, checklist lines, and instructions to ensure clarity for multilingual teams everywhere.
Usage
This section of the article aims to help you understand the translations functionality available for mobile users and the scope of translations that have been implemented.
Dynaway's mobile applications are configured to display data in the language that the application is set up for the customer. For multi-language support of applications master data, users can set up translations for certain fields which are supported by the application's translation module. If translations are set for mobile platforms and the user has selected the language for mobile, in such cases users will be able to see the entities, forms and fields data in the selected language.
Note that translated contents are only applicable for the entities/ fields which are supported for translations.
Below is the list of the entities currently supported for translation:
| Sl. No. |
Setup Table |
Translated |
Entity |
Notes |
|---|---|---|---|---|
| 1 | Asset types | name | ObjectType | |
| 2 | Attribute types | description | SpecificationType | |
| 3 | Attribute values | stringValue, description | SpecificationTypeValue | |
| 4 | Counters | name | ObjectCounterType | |
| 5 | Criticality types | criticalityName | WorkOrder | |
| 6 | Description | notesDescription | WorkOrderLine | Description on job type defaults |
| 7 | Fault area | description | FaultArea | |
| 8 | Fault cause | description | FaultCause | |
| 9 | Fault remedy | description | FaultRemedy | |
| 10 | Fault symptom | description | FaultSymptom | |
| 11 | Fault type | description | FaultType | |
| 12 | LOTO lifecycle states | name | SafeWorkLOTOStage | |
| 13 | Maintenance checklist template line | name, instructions | WorkOrderLineChecklist | |
| 14 | Maintenance checklist variable | name | ChecklistVariable | |
| 15 | Maintenance Checklist variable value | value | ChecklistVariableValue | |
| 16 | Maintenance downtime reason codes | name | ProductionStopType | |
| 17 | Maintenance job type variants | name | JobVariant | |
| 18 | Maintenance job types | name, notesDescription | JobType, WorkOrderLine | |
| 19 | Maintenance request lifecycle states | name | StageRequest | |
| 20 | Maintenance request types | name | RequestType | |
| 21 | Maintenance worker groups | name | WorkerGroup | |
| 22 | Models | description | ProductModel | |
| 23 | Service levels | name | WorkOrderPriority | |
| 24 | Trades | name | JobTrade | |
| 25 | Work order lifecycle model | name | StageWorkOrder | Lifecycle stages for work orders |
| 26 | Work order pools | name | WorkOrderPool | |
| 27 | Work order types | name | WorkOrderType |
To know more about setting up translations and the supported entities for translation, view the section on: Setting up Translation of Master Data.
Example:
- The scenario shown in screenshot 01 is a screen from Work execution app with work order job details. Here the current master data is in English.
- Now in screenshot 02, the same details is shown when the language selected is German. The fields marked in screenshot 01 are translated to German.
- As you can see, only some properties will be translated - This helps different people recognize the same data in the language of their choice.
- For example, for job type:
- "Type" = "Typ" (translated).
- "Calibration" = "Calibration" (ID is not translated).
- "Calibration" = "Kelibrierung" (name is translated).
- For example, for job type:
