Configuring the Help Experience for Dynamics 365 Business Central

The default version of Business Central comes with conceptual overviews and other articles that publish to the site. This location is then accessible from the Help menu and through the Learn More links in all tooltips. Each extension that you add will include its own tooltips and links to Help. But what if you want to deploy Business Central locally? Or if you have a vertical solution so that you want to refer your customers to your own website for Help? Or if you have a legacy Help collection based on the Dynamics NAV Help Server?

These and other scenarios are also supported in Business Central. But the options and possibilities are different, depending on your deployment scenario.

Apps for online tenants

When you build an app for Business Central using the AL developer experience, you are expected to comply with the Business Central user assistance model. This includes tooltips and context-sensitive links to Help.

For more information, see User Assistance Model and Configure Context-Sensitive Help.

On-premises deployments

For deploying Business Central on-premises, you must choose between using the legacy Dynamics NAV Help Server or an online website. Help Server is a simple website that requires your Help to be in a specific format (HTML files), and the online website can host any content that you want to make available. Your choice depends on the concrete needs of your solution and your users.


You can configure each client to use either an online library or Help Server. If you add configuration for an online library, you must remove the settings for Help Server.

Online library

If you want to use a website that is not based on Help Server, then you must specify the URL in the settings for the Web client. The website does not have to be publicly accessible, but it must be accessible to all users of the solution that it supports.

The navsettings.json file must contain the following setting in the ApplicationIdSettings element:

  "NAVWebSettings": {
    // [...more keys]
  "ApplicationIdSettings": {
    //BaseHelpUrl:  The location of Help for this application.,
    "BaseHelpUrl": "{0}/documentation/",
     // [...more keys]


Replace the value of the BaseHelpUrl key with the URL for your own website. The parameter, {0}, represents the locale of the browser that the user is using, such as en-us or da-dk, and is set automatically at runtime.

For more information, see Configuring Business Central Web Server Instances.

Help Server

If you want to use Help Server, then you must specify the server and port in the installation options. The Help Server website can also serve as a starting point for adding a library to your existing website, for example.

The navsettings.json file must contain the following settings in the NAVWebSettings element:

  "NAVWebSettings": {
    //HelpServer: Name of the Dynamics NAV Help Server to connect to.,
    "HelpServer": "",
    //HelpServerPort:  The listening TCP port for the Dynamics NAV Help Server. Valid range: 1-65535,
    "HelpServerPort": "49000",
    // [...more keys]
  "ApplicationIdSettings": {
    // [...more keys]

In the example, represents the URL to the Help Server instance. For more information, see Configuring Microsoft Dynamics NAV Help Server in the developer and adminstration content for Dynamics NAV.


If you use Help Server, the UI-to-Help mapping functionality that is described in Configure Context-Sensitive Help does not work. Neither does the original Help lookup mechanism that was based on filenames that reflected the object IDs, such as N_123.htm for the page object with the ID 123. For more information, see Blog post: Reusing classic object-based Help on your Dynamics 365 Business Central Help Server.


If you are upgrading from Microsoft Dynamics NAV 2017, you can reuse your existing Help Server content by simply replacing the product name and make any other changes that apply to your Business Central environment.

You can also still download the files that were made available for Microsoft Dynamics NAV 2017. The download consists of 45 CAB files with the content from the Dynamics NAV 2016 DVD rebranded to Microsoft Dynamics NAV 2017. There are CAB files with the W1 application Help translated into each of the supported languages plus the local functionality for the country/region where that language is spoken. There are also CAB files with local functionality in English. The files were published as a single download so each administrator could choose exactly the files that they needed at the time. For more information, see Microsoft Dynamics NAV 2017 Classic Help Download.

Known issues with Microsoft's content

Microsoft's content in the various GitHub repos is optimized for the site and the tools that are used for this site. If you reuse Microsoft's content, you may experience a number of known issues, depending on your deployment method. This section describes recommended steps to work around these issues.

Docs are not available for a specific version

Microsoft's public GitHub repos reflect the current version of Business Central. If you want to deploy help for an earlier version of Business Central on-premises, then you can use the HTML files on the installation media. If you find that that particular version is missing content, then please check the following sections for suggested workarounds.

If you deploy Microsoft's content to a website, your tools or your users will report that some links do not work. The links result in a 404 error or similar. These errors are caused by Microsoft having deleted the target files due to rework of the content. On the site, we have tools that automatically handle links to deleted files through redirection. But if you deploy Microsoft's content to your own website, or if you install the legacy Dynamics NAV Help Server from Business Central installation media, you don't have the same redirection.

We run periodic tests to catch these errors, but if you do see an error that is caused by a file not existing anymore, the trick is to check the .openpublishing.redirection.json file in the root of the source repo. This file is used by the site to manage redirection when a file is deprecated. So if you get an error that " does not exist", then you can see in the .openpublishing.redirection.json file that that article has been deprecated and replaced by So you can replace the link in the file that is looking for to link to instead.

ToC.xml for Help Server is different from the file

Microsoft does not currently maintain the ToC.xml file and does not add new features to it. While the Help Server component is still supported, it will be deprecated in the future. As a result, it contains links that are broken as described in the previous section.

Translated content is not available

Microsoft creates content in English (US) that then gets translated into the Microsoft-provided target languages. The translations are available in the relevant localization repos after a few weeks.

Fork the Microsoft repos, and customize or extend the content

If you want to customize or extend the Microsoft Help, you can fork our public repo for either the source repo in English (US) at, or one of the related repos with translations into the supported languages. For guidance about how to generate HTML files for your website, see Build HTML files. For more information, see Extend, Customize, and Collaborate on the Help.

See Also

User Assistance Model
Adding Help Links from Pages, Reports, and XMLports
Working with Dynamics NAV Help Server
Configuring Microsoft Dynamics NAV Help Server
Migrate Legacy Help to the Business Central Format
Building Your First Sample Extension With Extension Objects, Install Code, and Upgrade Code
Building an Advanced Sample Extension
Development of a Localization Solution
System Requirements
Resources for Help and Support
Blog post: Extending and customizing the Help
Blog post: Collaborate on content for Business Central
Blog post: Reusing classic object-based Help on your Dynamics 365 Business Central Help Server
Docs Contributor Guide
Docs Authoring Pack for Visual Studio Code