Configure Context-Sensitive Help

A key pillar of helping users help themselves is to give them access to Help for the particular corner of Business Central that they are working in.

App-level configuration

At an app level, you can specify where the Help for your functionality is published in the app.json file. For example, if you publish your content to, then you would specify that in the contextSensitiveHelpUrl property as shown in the following example:

  "contextSensitiveHelpUrl": "",

In this example, the contextSensitiveHelpUrl property specifies that the links to the Help must go to the site when the user is using your app's functionality across all locales. When the user is using functionality from the base application, then the Help calls will go to the default location on the site.

If your app only supports a limited number of locales, you can specify that as well as shown in the following example:

  "contextSensitiveHelpUrl": "{0}/documentation",
  "supportedLocales": [
    "en-GB", "en-IE

Localization apps

Specifically for localization apps that bring Business Central to new markets, the properties in the app.json file can be set to take over the links to Help for specific languages as shown in the following example:

  "helpBaseUrl": "{0}/documentation",
  "supportedLocales": [

In this example, the helpBaseUrl and supportedLocales properties specify that the links to the Help must go to the site when the user is using the product in either English (Ireland) or English (United Kingdom). If the user switches the application language to English (US), then the Help calls will go to the default location on the site.

Page-level configuration

Your target website is expected to have a default page that will display if nothing else is specified. But for each page or page extension, and for each field or field group on those pages, you can then specify the exact Help page that describes this page or field. You can do that using the ContextSensitiveHelpPage property as shown in the following example:

page 50101 "Reward Card"
    PageType = Card;
    SourceTable = Reward;
    ContextSensitiveHelpPage = 'sales-rewards';


In this example, the app contains a page object that is mapped to the sales-rewards Help file on the website that the app.json specifies. As a result, the Learn more link in the tooltips for this page will go to the equivalent of

You can use the ContextSensitiveHelpPage property to direct all Help calls to the same article, or to group the Help calls based on individual features or workflows. For example, Microsoft has chosen to group the context-sensitive links depending on the granularity of the Help for specific area in the base application. If the Help for a specific area is made more granular, then the context-sensitive Help mapping is updated accordingly.

You can set the ContextSensitiveHelpPage property on all pages, or only on those that you don't want to get the default Help page for your website. For page extensions, the value of the ContextSensitiveHelpPage property will apply only to the controls that the page extension adds to the extended page objects. For example, if your page extension adds two new controls to the base application's Customer Card page, then the Learn more links in the tooltips for those two controls will go to the Help page that you have specified, and the Learn more links in the rest of the controls will go to the default Help that is specified in the base application. This way, multiple apps can extend the same page object and each apply their own content-sensitive Help link without overwriting the context-sensitive links for other apps.

In contrast, the app.json file also contains a help property, but this specifies the link that describes the app or solution itself and is used by AppSource.

How it works for the base application

In the current version of Business Central, the context-sensitive links to Help for the base application works in a different way that is based on a UI-to-Help mapping that is stored in table 2000000198 Page Documentation. In this table, all page objects in the default version of Business Central are listed, and have a target Help article associated with each of them. This means that multiple page objects can be associated with the same Help article, such as when a specific workflow involves multiple pages.

The table associates page IDs with target articles, but the URL to where to find the target article is specified at the application level that defaults to the site. In an extension, you can overrule this URL so that all calls for Help go to your site instead, for example. This is especially important for localization apps where all context-sensitive Help calls for that app's language must go to that app provider's website.

See also

User Assistance Model
Resources for Help and Support for Dynamics 365 Business Central
Adding Help Links from Pages, Reports, and XMLports
Migrate Legacy Help to the Business Central Format
Development of a Localization Solution
Blog post: Extending and customizing the Help
Blog post: Collaborate on content for Business Central
Docs Contributor Guide
Docs Authoring Pack for Visual Studio Code