You can translate RapidValue elements that can be a part of your solution. You can translate the elements inside or outside D365 FO. To translate the elements outside D365 FO, for example by a translation agency, you can create an export file.
The D365 FO system language is the original language of your solution and its elements.
Prerequisites:
Name | Responsible | Description |
---|---|---|
Add translation |
Translator |
You can translate all RapidValue elements that can be a part of your solution. For each element record, you can create a translation. To help the translator, the not-yet-translated text is shown in the current language. |
Enter translation |
Translator |
If the translation is done inside D365 FO usually, the RapidValue element texts are translated from the Business process translation workspace. The translator can replace the not-yet-translated text with the translation. |
Export translations |
Translator |
You can export records to be translated outside D365 FO . For example, you can outsource the translation to a translation agency. As a result of the export, a Microsoft Excel file is created to which the to-be-translated records are added. This file is added to the Translation files tab on the Business process file share workspace. |
Translate records in file |
Translator |
To get the RapidValue elements texts translated, you can take the Microsoft Excel file with to-be-translated records and hand it over to the translator. In this file, in the Translated text column, the translator must replace the original texts with the translations. |
Import translations |
Translator |
If the texts in the Microsoft Excel translation file are translated, you can import the translations into RapidValue. Important
|
Mark translation to be redone |
Translator |
If you change text (for example, the name or description) for any record that is already translated, you can mark the translation to be redone. As a result:
|
Name | Responsible | Description |
---|---|---|
Add translation |
Translator |
You can translate all RapidValue elements that can be a part of your solution. For each element record, you can create a translation. To help the translator, the not-yet-translated text is shown in the current language. |
Enter translation |
Translator |
If the translation is done inside D365 FO usually, the RapidValue element texts are translated from the Business process translation workspace. The translator can replace the not-yet-translated text with the translation. |
Export translations |
Translator |
You can export records to be translated outside D365 FO . For example, you can outsource the translation to a translation agency. As a result of the export, a Microsoft Excel file is created to which the to-be-translated records are added. This file is added to the Translation files tab on the Business process file share workspace. |
Translate records in file |
Translator |
To get the RapidValue elements texts translated, you can take the Microsoft Excel file with to-be-translated records and hand it over to the translator. In this file, in the Translated text column, the translator must replace the original texts with the translations. |
Import translations |
Translator |
If the texts in the Microsoft Excel translation file are translated, you can import the translations into RapidValue. Important
|
Mark translation to be redone |
Translator |
If you change text (for example, the name or description) for any record that is already translated, you can mark the translation to be redone. As a result:
|
Related to | Notes |
---|---|
Set up translation parameters |
  |
Assign module to trainee |
  |
Manage translations |
  |