Today, the sequence to get translations for your developed captions/labels:

1)app.json: "TranslationFile" in features array,
2)Generate xliff files
3)Use Ms Lifecycles Service translation tool or do translation by yourself
4)Modify/improve translations & save them in Translations folder (and also backup)
5)Build extension

new)"Import xliff file on the extension."

"Import xliff file on the extension." is a new step: in an action on the extension management.

I should be a great issue if we can import the xliff file connected to the extension without compiling/build that extension. In other words: import the xliff file in Business central to modify the captions that way -> utile for editable report header captions.

Remark: to get it work properly, the ID's and the "original"-element in the xliff file must match the original xliff file. You still need a xliff file and language before installing it on your tenant.
Category: Development
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team