Business Central v29 quietly shipped a nice upgrade for developers working with ModuleInfo. If you’ve ever pulled module metadata using NavApp.GetCurrentModuleInfo, you already know the standard Runtime 17 fields: name, ID, version, publisher, dependencies, and so on.

With Runtime 18, we now get four new values that expose the module’s compliance and documentation metadata directly through AL; no more digging through app.json, manifests or having redundant information in the AL code.

What’s New in Runtime 18

These four fields are now available on the ModuleInfo record:

• ContextSensitiveHelpUrl
• EULA
• Help
• PrivacyStatement

This is especially useful for ISVs, AppSource apps, and anyone building extensions that need to surface or validate compliance‑related metadata programmatically.

Code Snippet

Here’s a quick example showing both the existing Runtime 17 values and the new Runtime 18 additions:

procedure ShowModuleInfo()
var
    Module: ModuleInfo;
begin
    NavApp.GetCurrentModuleInfo(Module); // Retrieves the current module's information

    // Runtime 17 Values
    Message('App Name: %1', Module.Name());
    Message('App ID: %1', Module.Id());
    Message('App Version: %1', Module.AppVersion());
    Message('Publisher: %1', Module.Publisher());
    Message('Data Version: %1', Module.DataVersion());
    Message('Dependencies: %1', Module.Dependencies());
    Message('Package ID: %1', Module.PackageId());

    // Runtime 18 Values
    Message('Context-Sensitive Help URL: %1', Module.ContextSensitiveHelpUrl());
    Message('EULA: %1', Module.EULA());
    Message('Help: %1', Module.Help());
    Message('Privacy Statement: %1', Module.PrivacyStatement());
end;

Why This Matters

These new fields make it easier to:

• Validate AppSource metadata at runtime
• Surface compliance information inside your own admin tools
• Build diagnostics pages or telemetry that include module documentation links
• Ensure your extensions expose the correct help and legal URLs

It’s a small addition, but a very welcome one; especially for teams managing multiple extensions or automated deployment pipelines.