- Feature
- Access application links through ModuleInfo
- Availability
- Generally available (October 2026)
- Industry focus
- Independent software vendors (ISVs) and AppSource publishers
For companies that build and sell Business Central apps, support quality is a competitive weapon. Customers judge an app partly by how easy it is to find help, licence terms and privacy information. Business Central 29.0 gives publishers a cleaner way to surface all of that, in the user's own language.
The industry challenge
A typical ISV publishes one or more apps on AppSource and sells into several countries. Each app has a set of important links:
- A help or documentation site
- An end-user licence agreement (EULA)
- A privacy statement
- Context-sensitive help pages for specific features
These links already live in the app manifest (app.json), because AppSource requires them. But when the app wants to show them inside Business Central, for example in a setup wizard, an About page or an error message, developers have often hard-coded the same URLs in AL code as well.
That duplication causes real problems. When a documentation site moves, someone has to find every hard-coded link. When the app is sold in a new country, local-language help pages need separate handling. Broken or outdated legal links can also become a compliance issue during procurement reviews.
What Microsoft delivered in Business Central 29.0
The ModuleInfo data type in AL now exposes more of the app manifest at runtime. According to Microsoft and an MVP walk-through of the release, an extension can now read:
- The help link
- The EULA link
- The privacy statement link
- The context-sensitive help link, which respects the current user's locale
These properties need AL runtime version 18.0 or later.
Microsoft frames the value as twofold. Extensions can show help, legal and privacy resources dynamically instead of copying links into code. And context-sensitive help can follow the user's locale, which improves support in multilingual deployments.
Where the value shows up
| Business area | Impact for an ISV |
|---|---|
| Maintenance | One source of truth for links, in the manifest |
| Customer support | Users land on help in their own language |
| Compliance | Legal and privacy links shown in the app always match what was published |
| International expansion | New markets don't need code changes to point at local help |
| Product quality | Fewer broken links in setup pages and error messages |
For a small publisher, the biggest gain is less maintenance work. Every release that doesn't need someone to hunt down hard-coded URLs is a release that ships faster.
A worked scenario
Consider an ISV that sells a warehouse barcode app in the UK, Germany and the Netherlands (an illustrative example). Its setup wizard includes a "Learn more" link, and its error messages point to troubleshooting articles.
Previously, those links were hard-coded in English. German and Dutch users landed on English pages, and support tickets rose after each launch. When the company moved its documentation to a new platform, a developer spent two days finding and fixing URLs across the codebase.
With Business Central 29.0, the developer reads the help and context-sensitive help links from ModuleInfo. Users get help in their own locale. The next time the documentation site moves, the team updates the manifest and ships a new version, with no hunt through the code.
Adoption considerations
- Check your runtime version. The new properties need runtime 18.0 or later, so plan the change alongside your next version update.
- Clean up the manifest first. Make sure the links in app.json are current and point to stable URLs.
- Organize help by locale. Locale-aware links only help if your documentation actually has local-language pages.
- Remove hard-coded links gradually. Search your codebase for URLs and replace them as you touch each area.
- Review legal links with your legal team. Treat EULA and privacy URLs as controlled content.
The bottom line
For Business Central ISVs, every hour spent on maintenance is an hour not spent on features customers will pay for. ModuleInfo app links in Business Central 29.0 remove a small but recurring source of maintenance work. They also give international customers a better support experience. It's the kind of quiet improvement that makes an app feel more professional.
If you publish Business Central apps, it's worth reviewing how your extensions surface help and legal content as part of your 29.0 update planning.
Sources: Microsoft roadmap 573354 · Dynamics 365 Lab: Access application links through ModuleInfo