Navigating Namespace Changes in Business Central 28
Business Central 28 introduces fully qualified names for pages, codeunits, reports, and record references, allowing developers to reference objects directly without requiring using statements at the top of files. This improves code clarity by making object origins explicit at the point of use.
post Aardvark Labs
"I don't need the namespace at the top of the file, and we are explicit as to where this page is coming from."
Key points
- Fully qualified names enable direct object reference without using statements
- Reduces namespace declarations at the top of files, preserving code space
- Applies to pages, codeunits, reports, and RecordRef objects
- Makes code more readable by showing object origin at the line level
Quotes
- “I don’t need the namespace at the top of the file, and we are explicit as to where this page is coming from.” (Highlights the key benefit of fully qualified names for code organization)
AL objects mentioned
As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.
- page 21 “Customer Card”
- report “Cash Applied”
- codeunit 81 “Sales-Post (Yes/No)”
- table 18 “Customer”
More than one object has this name, so none is linked: report “Cash Applied”.
Context
- Features: fully qualified names, namespace improvements, RecordRef support
- Versions: 28
Source: Aardvark Labs, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.