Currently Microsoft is updating BC Saas sandboxes to version 23.
When you create a new AL project (AL:Go!), and setup your launch.json and app.json files correctly and then try to download symbols, then you might get this error:
This AL extension version for Visual Studio Code cannot be used with the specified server. Please update the AL extension from the Visual Studio Code marketplace.
Additional information:
Server details
– Runtime: 12.1
– Web API: 6.0
– Debugger: 6.0
AL extension details
– Supported runtimes: 1.0, 2.0, 2.1, 2.2, 2.3, 2.4, 3.0, 3.1, 3.2, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 7.0, 7.1, 7.2, 8.0, 8.1, 9.0, 9.1, 9.2, 10.0, 10.1, 10.2, 11.0, 11.1, 12.0
– Supported Web API: 1.0, 2.0, 3.0, 4.0, 5.0, 6.0
– Supported debuggers: 1.0, 2.0, 3.0, 4.0, 5.0, 6.0
The solution or workaround is to switch to the pre-release version of the AL extension in VSCode:
After doing that and reloading the project, you can download symbols without any error.
Also, make sure that in your app.json you have:
and in your launch.json you have the correct environmentName and tenant parameters.
Because when you switch to the pre-release version of the AL extension and then create a new project (AL:Go!) it will use version 24 settings…
This workaround, switching to the pre-release version, imho, is a bug and the error should not happen at all…
Update:
- More information available here: Cannot publish (or debug) to BC 23 through VS code (AL language extension for BC 12.1) · Issue #7554 · microsoft/AL (github.com)
- Debugging a BC Saas sandbox does not seem to work anymore…
Discover more from think about IT
Subscribe to get the latest posts sent to your email.