Business Central 2026 release wave 1 (BC28): Run AL objects and open record references using fully qualified names (Support for namespaces and fully qualified names)

Hi, Readers.
The public preview for Dynamics 365 Business Central 2026 release wave 1 (BC28) is available. Learn more: Link.

I will continue to test and share some new features that I hope will be helpful. In this post, I would like to talk about Run AL objects and open record references using fully qualified names.

Run AL objects and open record references using fully qualified names:

New method overloads have been introduced to support running codeunits, pages, and reports using their fully qualified names. Additionally, RecordRef.Open can now be invoked with the fully qualified name of a table.
Feature details in update 28.0 public preview for 2026 release wave 1 – Business Central | Microsoft Learn

This is also mentioned in the AL Changelog (Business Central 2026 release wave 1).
Support for namespaces and fully qualified names:

Let’s see more details.

Namespaces are used to organize code into logical groups and hierarchies, which can prevent naming conflicts that can occur when libraries are combined. Namespaces ensure uniqueness in code names and allow reuse of names in different contexts, and provide structure for the code base, making it easier to navigate and understand. Namespaces are used in many programming languages and with Business Central they’re available with AL.
Standard Object: table 18 Customer

Custom object:

With this wave (BC28), new method overloads are introduced to support running codeunits, pages, and reports using their fully-qualified names. Additionally, RecordRef.Open can now be invoked with the fully-qualified name of a table.

Record and RecordRef instances now expose a FullyQualifiedName property.

For example, the following codeunit 80 “Sales-Post” can be run using the following statement.

Codeunit.Run('Microsoft.Sales.Posting."Sales-Post"');

Another example: The following statement will run page 4, “Payment Terms”.

Page.Run('Microsoft.Foundation.PaymentTerms."Payment Terms"');

Record and RecordRef instances now expose a FullyQualifiedName property, for example:

Great, give it a try!!!😁

PS:
1. Dynamics 365 Business Central: Where to find all standard AL namespaces? (Download all AL namespaces)

2. Business Central 2025 wave 2 (BC27): New field “AL Namespace” has been added to object metadata record (AllObj, AllObjWithCaption, Page Metadata, Report Metadata, and Codeunit Metadata)

END

Hope this will help.

Thanks for reading.

ZHU