In Business Central 24 Release Wave 1 (Runtime 13.0), it will be possible to add tooltips for fields directly in the corresponding tables. This eliminates the need to specify a tooltip on a page for every field and centralizes them on the tables.
In this blog post, we will show you how you can move your tooltips to tables without the need of manually copy and paste. Please note that you need to provide translations for the moved tooltips. You can rely on free tools to do this OR you can use our tool BEYOND Translations to automatically translate the file with just one click. For more information about our tool Beyond Translation check out the Beyond Translations blog post or visit the official Beyond Translations landing page.
Move your tooltips to the tables
Let's start with moving the tooltips to the tables. Instead of copy and paste the tooltips from pages into the table one by one, you can use the code actions to move the tooltips.
Hover your mouse on a tooltip on a page and click the light blub in VS Code. Then choose the option to move the tooltip to the corresponding table.
By using this option the tooltip is moved to the source table of the field.
Please note that the moving of tooltips will lead to a new global translation file in which the indexes for the translations are changed. This will affect the target language translation files (such as ".de-DE.xlf") as well and will delete all translations when you synchronize translations from the global translation file. Therefore you should make a backup of the target language translation files.
Save Time when translating the moved tooltips
In this section, we will show you how to save time when you have to re-enter the translations after moving the tooltips to the tables.
If you are not able to package your app due to an AL0666 error (or if you are not able to use the code action to move the tooltip to the corresponding table), you need to change the runtime of your app. Go to your app.json file and change the value of the runtime:
"runtime": "13.0"Learn more about runtimes in the Microsoft Learn and read our blog about runtimes:
If you app doesn't build a translation file, you need to specify this in your app.json file:
"features": [ "TranslationFile" ]Package your app to create a new g.xlf file with the updated translations unit index. Then, you need to synchronize these translation units from the g.xlf file to the target language xlf file.
You can now use common free tools like NAB Tools or the XLIFF extension for VS Code, but if you need to handle big or multiple target translation files this can be a time-consuming job. You can save some time when you download the base application translation files and match them with the NAB tool.
If you are looking for a solution to translate target files quickly and easily with just one click, try Beyond Translations. Contact us for a demo appointment. The tool is seamlessly integrated into Azure DevOps and we will also soon be able to offer the solution for Github.
info@beyondit.gmbh
Comentarios