AL icon indicating copy to clipboard operation
AL copied to clipboard

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual...

Results 305 AL issues
Sort by recently updated
recently updated
newest added

**1. Describe the bug** I do have two extensions A & B in multi-root project setup. Extension B, depends on Extension A. Extension A is using symbols from W1 Extension...

requires-triage
workspaces

Hello, It looks like adding an OnLookUp() trigger in a pageextension to override the existing OnLookUp() on a page isn't working anymore from version 21.1 onwards. When we add a...

accepted

- Issue Type: `Bug` - Extension Name: `al` - Extension Version: `10.0.687650` - OS Version: `Windows_NT x64 10.0.19043` - VS Code version: `1.71.2` :warning: We have written the needed data...

al-core-compiler
workspaces
accepted

The dynamicsuser.net forum no longer exists:

**1. Describe the bug** The VS Code sticky scroll feature works fine on al files. However, when drilldown to the base app symbols, a .dal file is opened which does...

workspaces

Hello, in this scenario: - On Prem - Windows Server 2022 - Business Central 20 (47024) - Authentication mode Windows You cannot download symbols from Visual Studio Code (with latest...

input-needed
vscode-integration

Having unrelated XML files that aren't for permissions in a repository is problematic because these Cops try to scan them, find stuff they don't expect, and crash. They should instead...

static-code-analysis
AppSourceCop
PerTenantExtensionCop
accepted

According to [here](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-table-system-fields#audit), the fields SystemCreatedAt, SystemCreatedBy, SystemModifiedAt, SystemModifiedBy - are only usable from BC17 onwards. So we merrily used them... in a project targeting BC15+. Which builds fine, and...

al-compiler-validation
accepted

When applying code fix action for implicit with warning (AL0606), action is overdoing it for SETRANGE statements. There is no need to use epxlict table name in the first param...

requires-triage
code-fixer

**1. Describe the bug** Sorry for this poor description as well, I'm just trying to log some errors hoping you can see something in the callstack. But unfortunately I don't...

requires-triage