Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Mysolution AL HelperNew to Visual Studio Code? Get it now.
Mysolution AL Helper

Mysolution AL Helper

Mysolution BV

|
751 installs
| (3) | Free
VS Code Extension to aid the Mysolution Developer doing his daily source control tasks
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

MysALHelper README

This extension has been created to make the life of the Mysolution AL Developer easier. From time to time, new features will be added to this extension.

The functionality in this extension is basically grouped into 2 sections:

  • General availability Everyone developing AL applications can use this.
  • Mysolution Internal availability Functionality useable for Mysolution internal people only (i.e. because it's designed talk to an internal web service)

Features

General available

  • Build app and create Translation file (Missing Captions)
  • Build app and create Translation file (All Captions)
  • Build app and create Translation file (Current Object Missing Captions)
  • Build app and create Translation file (Current Object All Captions)
  • Process Translation file and Publish local (for testing)
  • Process Translation file and Publish local (with debug, for testing)
  • Process Translation file, keep the xlf and Publish local
  • Process Translation file and keep the xlf (no publishing)
  • Uses Microsoft Translator Cognitive services to do auto-translation

Mysolution Internal available only

  • Possibility to pick the first available object id from a central database and reserve it
  • Possibility to remove the reseration for a previous reserved object id
  • Snippets for definition of vars for most used Mysolution tables

Translation

These translation functions create a CSV file for each configured locale by comparing the compiler-generated global XLIFF with the locale XLIFF. Missing captions include absent or empty targets, targets marked as new or needing translation, changed English source text, and unexpected translation IDs. Legacy IDs are accepted when TranslationsWithNamespaces is enabled.

Existing non-empty CSV translations are matched by both element and current English source. They are kept intact and reported separately as awaiting XLIFF processing; outdated CSV translations are not reused as current translations.

The CSV file is shared per branch: <app folder> (<branch>).<locale>.Translations.csv. Characters that are invalid in file names are replaced by -; a detached HEAD uses detached as branch name. Existing per-user files keep being processed. On main, master, release/* and hotfix/*, the extension asks for confirmation before building or creating translations. The PowerShell script refuses protected branches unless this confirmation was explicitly passed.

  • Mysolution Internal | The created csv file(s) can then be edited and checked in to Devops. The build pipeline will then take the csv file and process it into the master xlf file.
  • General | You can run the "Process" commands to process the language files locally.

Automatic Translate

You can use the free Microsoft Translator service for translating up-to 2 million characters.
Go to: https://www.microsoft.com/en-US/translator/business/trial/ and check the section "Develop your own app"

Questions, Suggestions, Bugreports

Please send them to Herman van den Born

Development

Install and Package

Install node_modules by running the following command in the root of the project:

npm install

After that, you can run the following command to package the extension:

vsce package

This will create a .vsix file in the root of the project. You can install this file in Visual Studio Code by using the command palette (Ctrl+Shift+P) and selecting "Extensions: Install from VSIX...".

Testing and Debugging

To test and debug the extension, you can use the built-in debugging features of Visual Studio Code. You can set breakpoints in your code and run the extension in a new instance of Visual Studio Code. By going to the debug tab (Ctrl+Shift+D) and selecting "Run Extension" from the dropdown menu, you can start debugging the extension. This will open a new instance of Visual Studio Code with the extension loaded, allowing you to test its functionality.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft