Gerardo Rentería Blog

7/3/2024

AL Language extension for Microsoft Dynamics 365 Business Central version 13.1.1065068 (New version)

[ESP] En el siguiente enlace puedes ver leer los cambios relacionados a la versión vigente:

[ENG] En el siguiente link, you can read the changes related to the current version:

MarketPlace Visual Studio: Change Log

13.1

Github Issues

#7661 The ID for the Field is not valid. It should be within the range, which is allocated to the application.
#7714 Unexpected warning AS0098 when adding an enumextension to an enum within the same AppSource app
#7745 Debugger crashes at random points

AppSourceCop

Updated rule AS0032 to allow removing non-obsolete page fields using as source a table field marked with obsolete state Removed.
Updated rule AS0032 to allow removing non-obsolete page part controls using as source a page part which has been removed.
Updated rule AS0031 to allow removing non-obsolete page actions whose name conflicts with a new action from the base page.
Updated rule AS0032 to allow removing non-obsolete page controls whose name conflicts with a new control from the base page.
Updated rule AS0033 to allow removing non-obsolete page views whose name conflicts with a new view from the base page.
Updated rule 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 and AS0098 to allow for skipping affixes if an extension objects extends a base object from the same publisher.
Updated the rule 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 to recommend that two-level namespaces should be used

Miscellaneous

The 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.
Fixed an error that was thrown when handling the textDocument/documentSymbol request.
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.
Updated AA0194 and AA0218 to validate actions of FileUploadAction type.
RAD publishing could fail in scenarios a new file was added.

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.