Use the of the label where it was defined Otherwise, translations are only used to translate labels in the same app.įor apps where translations are meant to translate the current app, the generated xliff file will have the correct value of the app name. When translating other extensions, make sure that the attribute original in the element in the xliff file is not set to the name of the current app. When your extension is then built and published, change the language of Dynamics 365 Business Central to view the UI in the translated language. DeWitt Jr., award-winning editor of the 144-year-old The Hampton County Guardian and a journalist for USA Today Network South Carolina, has authored Wicked Hampton County. Create a directory named Translations, in the root of the extension, and place the translated xliff file there. When the dependencies are set, you can add xliff files in your current project that translates the object captions of the referenced extension. To translate other extensions, for example, when adding translations to the Base Application, you must reference the project to be translated using the dependencies section in the app.json file. When the extension is built and published, you can change the language of Dynamics 365 Business Central to view the UI in the translated language. There is no enforced naming on the file, but it's a good practice to name it.

If you translate your extension to multiple languages, you must have a translation file per language. This is illustrated in the example below. The attribute corresponds to the object ID in the extension.

The target-language must be specified in the format '-', for example 'da-DK', 'es-ES', or 'de-DE'. For the translation, you'll now have to add the target-language and a element per label. xlf file, you can see a element for each label. LabelName = 'Label Text', Comment='Foo', MaxLength=999, Locked=true Īnd the following is the syntax for Label data types: varĪ : Label 'Label Text', Comment='Foo', MaxLength=999, Locked=true Use the same syntax for report labels: labels For more information, see Label Data Type. The comment, locked, and maxLength attributes are optional and the order is not enforced. The label syntax is shown in the example below for the Caption property: Caption = 'Developer translation for %1', Comment = '%1 is extension name', locked = false, MaxLength=999 The default behavior is that these elements aren't generated. The syntax is as follows: 'features': ĪPPLIES TO: Business Central 2020 release wave 2 and laterīy setting the GenerateLockedTranslations flag in the app.json file, you specify that you want to generate elements for locked labels in the XLIFF file. For the table fields, the OptionCaption is used. If the object already has a Caption property set, that value will be used. Make sure to rename the translation file before building the extension next time, as it'll be overwritten.īy setting the GenerateCaptions flag in the app.json file, you specify that you want to generate captions based on the object name for pages, tables, reports, XMLports, request pages, and table fields.

Online xliff editor