Share This Post

NAV Updates

Dynamics NAV Additional Components

NAV Additional Components

The NAV Additional Components listed in this section extend the capabilities Microsoft Dynamics NAV 2018 in various ways.

The following NAV Additional Components can also be installed with Microsoft Dynamics NAV 2018 Setup:

  • Automated Data Capture System
  • Microsoft Office Outlook Add-In
  • Microsoft Dynamics NAV Web Client
  • Microsoft Dynamics NAV Help Server
  • Deploying Microsoft Dynamics NAV Using ClickOnce

Automated Data Capture System

ADCS

ADCS

The Automated Data Capture System (ADCS) is a Dynamics NAV tool that lets you accurately capture data for inbound, outbound, and internal documents, primarily for warehouse activities. With ADCS, company employees use handheld devices and radio frequency technology to continuously validate warehouse inventories.

Installing ADCS

Installing ADCS

Installing ADCS

To install ADCS, you must customize the list of installation NAV Additional Components to include ADCS, which is not included in one of the predefined Installation Options.

Synchronizing Dynamics NAV with Outlook

NAV Additional Components uses the Microsoft Office Outlook Add-In component to synchronize data, such as to-dos, contacts, and tasks, between Dynamics NAV and Outlook. The Microsoft Office Outlook Add-In uses Dynamics NAV web services.

Installing Microsoft Office Outlook Add-In

You must install the Microsoft Office Outlook Add-In and other components before you set up Microsoft Office Outlook Integration. The following lists show which components and sub-components you must select in Dynamics NAV Setup.

These NAV Additional Components are not all available with any of the pre-configured Installation Options. To install the add-in, choose Custom on the Choose an Installation Option pane in Setup and then select components.

It is not necessary to install all listed components on a single computer. But if you install different Dynamics NAV components on different computers, then you must configure the NAV Additional Components so that they can communicate. The following table lists the components that need to be installed and configured.

Required components Required option
 Client  Not applicable
 Server  Microsoft Office Outlook Integration
 SQL Server Database Components  Demo Database
 Microsoft Office Outlook Add-In  Not applicable

Working with Microsoft Dynamics NAV Web Client

The Microsoft Dynamics NAV Web client gives users access to Dynamics NAV data over a network, such as the Internet, by using a web browser. Users can view and modify data from a user-friendly interface that resembles the Microsoft Dynamics NAV Windows client, where the starting point is the Role Center. The Role Center can be customized to users individual needs based on their role, company, and daily tasks.

Unlike the Microsoft Dynamics NAV Windows client, you do not have to install any Dynamics NAV components on devices that users will use to access Dynamics NAV data. The Microsoft Dynamics NAV Web client does not replace the Microsoft Dynamics NAV Windows client but complements it by enabling scenarios that are not possible with the Microsoft Dynamics NAV Windows client. For a visual overview of the Microsoft Dynamics NAV Web client, see Touring the RoleTailored Client for Developers.

Deploying the Microsoft Dynamics NAV Web Client

To deploy Microsoft Dynamics NAV Web client, you install and configure the Microsoft Dynamics NAV Web Server components on a computer that is running Internet Information Services (IIS) and has a connection to a Microsoft Dynamics NAV Server and database. Dynamics NAV users can access the Microsoft Dynamics NAV Web client from any supported device that has a supported internet browser and a TCP/IP network connection. For a list of supported devices and browsers, see System Requirements for Microsoft Dynamics NAV.

Developing for the Microsoft Dynamics NAV Web Client

As a developer of Microsoft Dynamics NAV Web client applications, you will have the same experience as developing Microsoft Dynamics NAV Windows client applications. You use the Microsoft Dynamics NAV Development Environment to create objects, such as pages and reports, and implement the same business logic as you would for the Microsoft Dynamics NAV Windows client. The same page or report that is displayed in the Microsoft Dynamics NAV Windows client can also be displayed in the Microsoft Dynamics NAV Web client.

Administering Users of Microsoft Dynamics NAV Web Client

Like the Microsoft Dynamics NAV Web client, you control access to the Microsoft Dynamics NAV Web client and Dynamics NAV data by creating user accounts, permission sets, and profiles. You do not have to set up separate user accounts for the Microsoft Dynamics NAV Web client and Microsoft Dynamics NAV Windows client. The permissions that are granted to a specific user account apply to all RoleTailored clients.

Working with Dynamics NAV Help Server

Dynamics NAV Help deploys to a Dynamics NAV Help Server, which is a website that installs on the specified server. The website includes Search and other navigation, and it provides context-sensitive Help for Microsoft Dynamics NAV Web client in addition to Microsoft Dynamics NAV Windows client. Depending on your deployment architecture, you can choose to set up a dedicated Help Server that all clients connect to, or you can choose to deploy customer-specific Help Servers.

Accessing Dynamics NAV Help

When you have deployed a Dynamics NAV Help Server, users in the Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client can access Help by pressing F1 or choosing a Help icon.

If you want to access the Dynamics NAV Help in a browser, enter the address for the Help Server, such as http://MyServer:49000/main.aspx?lang=en&content=across-get-started.html. You can save the URL as a favorite in your browser, and you can save links to individual Help topics such as http://MyServer:49000/Main.aspx?lang=en&content=ui-across-business-areas.html.

For example, if there is a complicated task that you have to do periodically, you can find the topic that describes how to do that task, and you can save the URL to the topic to your desktop or your favorites.

The URL to a Help topic contains two query parameters as described in the following table.

Name Description Example
 lang  Specifies the locale.

Dynamics NAV defaults to the Help content in the non-locale-specific version if the   client locale cannot be found.

 da-dk
 content   Specifies the HTML file that contains the relevant Help content.  across-get-     started.html

In the standard Help, most Help topics have easily recognizable file names, such as across-get-started.html for the conceptual overview that is called Getting Started.

Versions older than Microsoft Dynamics NAV 2017

In the standard Help for older versions of Dynamics NAV, many file names for topics had a prefix that identifies the type of content that the topic contains. The following table describes the prefixes for file names.

Name Description
 con  The topic contains a conceptual overview.
 B_  The topic contains reference content for a batch job.
 N_  The topic contains reference content for a page.
 ori  The topic is an orientation topic that provides an overview of a group of topics.
 R_  The topic contains reference content for a report.
 ref  The topic contains reference content for the Microsoft Dynamics NAV Development Environment.
 S_  The topic contains reference content for a system window or dialog.
 T_  The topic contains reference content for a table or a field on a table.
 tsk  The topic is a task topic and contains procedures.
 wlk  The topic contains a walkthrough.

 

Deploying Using ClickOnce Hosting on a Web Server

Hosting on a web server is similar to hosting on a file share. Using the steps outlined in the previous section, you should note that the two links in the deployment manifest should point to the http://address, instead of a \\fileshare address. This is the only change that you need to make to the files.

All the logic needed for requesting user permissions to install or check for upgrades happens on the client computer. The web server works like a file repository.

The only problem with web server hosting is that web servers use different file types differently. For example, by default a file that has the .config extension will not be able to be downloaded from a web server. The web server will restrict access to it. To work around this, you can create a web.config file in the folder that contains the application files, with contents similar to the following.

<?xml version="1.0" encoding="UTF-8"?>  
<configuration>  
  <system.webServer>  
    <directoryBrowse enabled="true" />  
    <staticContent>  
      <mimeMap fileExtension=".config" mimeType="application/x-msdownload" />  
      <mimeMap fileExtension=".tlb" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".olb" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".pdb" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".hh" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".xss" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".xsc" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".stx" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".msc" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".flf" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".rdlc" mimeType="application/x-msdownload"/>  
      <mimeMap fileExtension=".sln" mimeType="application/x-msdownload"/>  
</staticContent>  
    <security>  
      <requestFiltering>  
        <fileExtensions>  
          <remove fileExtension=".config" />  
        </fileExtensions>  
      </requestFiltering>  
    </security>  
  </system.webServer>  
</configuration>  

You should start with an empty .config file, and then use trial-and-error to add the necessary rules, until ClickOnce can download all the files. If ClickOnce cannot download the files, a report will show which file and which extension is the problem.

Requiring End Users to Read and Accept Software License Terms

End users who install the Microsoft Dynamics NAV Windows client are required to accept the Microsoft software license terms. By using the traditional Microsoft Dynamics NAV Windows client installer, this occurs as part of the installation process. However, by using ClickOnce deployment, this cannot occur as part of the installation process, and it must therefore occur before the ClickOnce process is started.

If you decide to deploy the Microsoft Dynamics NAV Windows client using ClickOnce, then it is your responsibility that end users accept the Microsoft software license terms before the installation. We recommend that you also require end user acceptance of your software license terms and any third-party software license terms that are part of the ClickOnce deployment.

To help you with this process, you can use the NAVClientInstallation.html template web page that was installed as part of the ClickOnce Installer Tools. When you try to open that file, you must select the Accept check boxes before you can install the Microsoft Dynamics NAV Windows client. You can design your own web page, as long as the process for the end user is the same. The end user cannot install the Microsoft Dynamics NAV Windows client until he has accepted the software license terms.

Upgrading to a New Version of the Dynamics NAV Client

If you want to push a new version of the Microsoft Dynamics NAV Windows client out to end users, you must do the following:

  • Produce a new ApplicationFiles folder. Follow the process that you used to create the first version, but assign a larger version number to the application manifest. You can replace the old application files in \\fileshare\clickonce\Deployment\ApplicationFiles, or you can put the new files in a new directory, such as \\fileshare\clickonce\Deployment\ApplicationFiles2. Make sure to run mage.exe -update to update the application manifest’s file list and hash values. Run mage.exe -sign to sign the application manifest.
  • Run mage.exe -update to update the deployment manifest’s reference to the application manifest as well as its hash value. Update the deployment manifest’s version number. Run mage.exe -sign to sign the deployment manifest.The upgrade check is based on the deployment manifest’s version. This is the version of the Microsoft Dynamics NAV Windows client that will be installed if a user installs Dynamics NAV for the first time. The deployment manifest also contains a minimumRequiredVersion. If a previously installed Microsoft Dynamics NAV Windows client has a version that is less than minimumRequiredVersion, then the user is forced to upgrade the Microsoft Dynamics NAV Windows client. This will appear similar to the following.
<assemblyIdentity name="Microsoft Dynamics NAV" version="11.0.0.0" … />  
  <deployment install="true" minimumRequiredVersion="11.0.0.0">  
    <subscription>  
      <update>  
        <beforeApplicationStartup />  
      </update>  
    </subscription>  

The <update> tag determines when the upgrade check is performed. In the example earlier in this section, beforeApplicationStartupwas specified, which means the upgrade check will be performed before the Microsoft Dynamics NAV Windows client starts and the user will experience a short delay every time that the Microsoft Dynamics NAV Windows client is started. If you want the upgrade check to be performed in the background every time that the Microsoft Dynamics NAV Windows client is started, then use the following setting.

<update>  
        <expiration maximumAge="0" unit="days" />  
      </update>  

With this setting, the user will be able to run the Microsoft Dynamics NAV Windows client without any delay. In the background, ClickOnce will check if the current version is too low. ClickOnce will enforce the upgrade the next time that the Microsoft Dynamics NAV Windows client starts. If you want to check for updates, such as every 14 days, then add maximumAge=”14”.

The application manifest version number can be changed independently of the deployment manifest version number. If you change the version number in the deployment manifest, but keep referring to the same version of the application manifest, then the user will experience that the Microsoft Dynamics NAV Windows client is upgraded, but nothing will occur because the new version of the deployment manifest will still point to the same application version. For example, this can be useful if you want to change the frequency of the upgrade checks or change the text in the Start menu.

Security Considerations

Installing any application on the local computer requires that you consider whether it is safe to do this. For a ClickOnce deployment of the Microsoft Dynamics NAV Windows client, here are some recommended security measures that you should consider:

  • Internal deployment – If you host the ClickOnce deployment on an internal file share or website, we recommend that you sign the ClickOnce deployment so that end users will not see an Unknown publisher message during installation. However, it is also acceptable not to sign the ClickOnce deployment.
  • Public deployment – If you host the ClickOnce deployment in a public location, we recommend that you sign the ClickOnce deployment and host it on a secure website (https://). Taking these precautions will reduce the risk of end users installing applications from bad sources and locations.

Limitations of ClickOnce Installed on the Microsoft Dynamics NAV Windows Client

The following are limitations of ClickOnce installed on the Microsoft Dynamics NAV Windows client.

Command-line arguments – ClickOnce installed on the Dynamics NAV client cannot be run with custom command-line arguments. For example, this affects the following scenarios:

  • An end user cannot specify the Home page.
  • An end user cannot specify a profile. He can only use his default profile.
  • An end user cannot disable personalization. An administrator can disable personalization on a profile.
  • An administrator cannot configure profiles. He should use the MSI-installed client for this task.
  • An end user cannot run in full-screen mode.
  • An end user cannot disable the navigation pane.Hyperlinks – The protocol handler dynamicsnav:// is not registered during ClickOnce installation, which means that the Dynamics NAV client cannot be activated by choosing a hyperlink. This could impact the following scenarios:
  • End users cannot send each other links to specific pages.
  • An end user cannot use the link on a OneNote page.
  • An end user cannot use the link on a report.
  • The debugger cannot be started.External components calling the Microsoft Dynamics NAV Windows client – A ClickOnce-installed Microsoft Dynamics NAV Windows client will be installed in a randomly generated folder, and when it is upgraded to a new version, it will be installed a new randomly generated folder. This means that external components will not be able to detect where the Microsoft Dynamics NAV Windows client executable is located. This could impact the following scenarios:
  • An end user can send a list page to Excel, but cannot refresh data from the Excel application.
  • Third-party applications cannot start the Microsoft Dynamics NAV Windows client.

Share This Post

Leave a Reply

avatar
  Subscribe  
Notify of
Skip to toolbar