---
id: release/al-13.1
type: release
title: AL Language extension 13.1
summary: "AL Language extension 13.1 for Business Central 2024 release wave 1 (BC24): released 2024-07-03; 4 changelog entries, 2 GitHub issues linked."
tier: official
language: en
system: development
tags:
  - github issues
  - appsourcecop
  - relaxing appsource affix and id range validation for apps
  - miscellaneous
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-09T15:15:16.963Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: ca309b61b431c637e22603742156f423dc103f2a03c62c4de25412095c6e03ef
evidence:
  - kind: marketplace
    url: https://marketplace.visualstudio.com/items/ms-dynamics-smb.al/changelog
    title: AL Language extension changelog, version 13.1
    date: "2024-07-03"
    commit: null
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
source_id: al-language-extension
extension: ms-dynamics-smb.al
version: "13.1"
wave: 2024 release wave 1
major: "24"
preview_at: null
released_at: "2024-07-03"
published_at: "2024-07-03"
prerelease: false
entry_count: 4
issues:
  - 7714
  - 7745
changes: []
---

# AL Language extension 13.1

> AL Language extension 13.1 for Business Central 2024 release wave 1 (BC24): released 2024-07-03; 4 changelog entries, 2 GitHub issues linked.

[Changelog on the Visual Studio Marketplace](https://marketplace.visualstudio.com/items/ms-dynamics-smb.al/changelog) · Business Central 2024 release wave 1 · BC24

## GitHub Issues

- [#7714](https://github.com/microsoft/AL/issues/7714) Unexpected warning AS0098 when adding an enumextension to an enum within the same AppSource app
- [#7745](https://github.com/microsoft/AL/issues/7745) Debugger crashes at random points

## AppSourceCop

- Updated rule [AS0032](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0032) to allow removing non-obsolete page fields using as source a table field marked with obsolete state Removed.
- Updated rule [AS0032](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0032) to allow removing non-obsolete page part controls using as source a page part which has been removed.
- Updated rule [AS0106](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0106) to allow removing non-obsolete protected variables, defined in extension objects, whose names are conflicting with the names of variables defined in the target object.
- Updated the rules [AS0011](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0011) and [AS0098](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0098) to allow for skipping affixes if an extension objects extends a base object from the same publisher.
- Updated the rules [AS0011](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0011) and [AS0098](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0098) to allow for skipping affixes if an object is defined in a namespace.
- Updated the rule [AS0013](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0013) to allow for using the ID range of a base table, when a table extension targets a base table from the same publisher.
- Added the rule [AS0127](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0127) to recommend that two-level namespaces should be used

## Relaxing AppSource affix and ID range validation for apps

Affixes no longer need to be added to extension members on apps from the same publisher. Furthermore, table extension fields will be able to use the ID range of the base table, if the base table is from the same publisher. The purpose of affixes and ID ranges is to ensure there are no conflicts between apps from different publishers. With this change, publishers have more flexibility in designing their apps, but will also have to ensure that there are no conflicts
within their own apps. You can see this in detail in our [documentation](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-checklist-submission-faq#questions-about-names-affixes-and-id-ranges).

## Miscellaneous

- Fixed an error that was thrown when handling the `textDocument/documentSymbol` request.
- The [AL1156](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/diagnostics/diagnostic-al1156) warning diagnostic was added when comments are used in the manifest file of an application. Its purpose is to help the interoperability of AL with various CI/CD integrations which may not support comments in json files, a scenario which leads to failures that are hard to detect and debug. The warning can be suppressed via a ruleset or the `suppressWarnings` property in the manifest file.
- Fixed an issue where the compiler would sometimes fail with internal errors during the validation of an interface implementation.
- When using "Attach debugger to this session" and "Explore page in Visual Studio Code" links form the web client, the configuration in VS Code will use the environment's runtime version instead of the latest available.
- RAD publishing could fail in scenarios a new file was added.
- Fixed an issue where compilation could fail with MissingTypeSymbol after changing a dependency's name or publisher

Source: Visual Studio Marketplace, ms-dynamics-smb.al changelog, Microsoft's text unchanged. Dates from the gallery's upload records.