Skip to main content
insightsoftware Docs insightsoftware Docs
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Create a Dynamics NAV Jet Remote Data Source - Users' Guide

Related Articles...

Overview

If your Dynamics NAV resides on a different network domain than does your installation of Microsoft Excel, System Administrators can use the JRDS Admin Guide to help them configure the Jet Remote Data Service.

Once a that service is set-up, users of the Jet Excel add-in can configure a data source to use the service.

Configuring the Data Source Connection

The first step in the Jet add-in is to create a new data source of the type Dynamics NAV 2013 - 2018 with a connection type of Remote Data Service .  Next, the authentication needs to be configured. These options are the same credentials that are used to access NAV.

The user can authenticate against the JRDS using any one of the following:

  1. Their own Windows credentials (this usually only applies to demo environments)
  2. Another user's Windows credentials (e.g., a user on a different domain - usually the domain where the data resides)
  3. NAV User Password credentials.

You will need to contact your system administration to obtain the exact settings being used in your organization.

In this example, Windows authentication is selected for a user account on a separate domain.

To create a new data source connection to your NAV database, start by selecting Settings > Data Source Settings from the Jet ribbon.

  1. On the Data Source Settings window, click the Add button. When the Add Data Source dialog will appear, provide a unique name for our NAV data source, select Dynamics NAV 2013 - 2018 for the Database Type , and Remote Data Service for the Connection Method.

  2. It is expected that users will be provide with a domain name, user name, and password to use for authentication - the same authentication information used to connect to the NAV Role-Tailored Client (RTC) or Web Client.

    auth_tab.png

  3. The connection information for the instance of the JRDS must be configured:

    connection_tab.png

  4. Note that the S erver is the one which is hosting IIS and the JRDS.  The Port is the one which was entered into PowerShell when the Application Container was created.  The Instance is the name entered into PowerShell when the Service Instance was created.

    The dropdown to select the company will populate when opened if the settings are correct.

    All remaining settings are typical of other NAV data source types.  Be sure to select the desired Drilldown type and, in the case or RTC drilldown, the directory where the RTC is installed.

  5. Once the Data Source Settings are correct, you can test them by clicking the Test Connection button at the top of the Data Source Settings window and should see the Test Connection Succeeded message. If there are any issues, the message should help you in troubleshooting.

When upgrading versions of Jet Excel add-in to a much newer release, ensure that both the Jet Remote Data Service installed on the server and the Jet add-in are on the same version to reduce potential issues.

Related Articles

Published:

Create a Dynamics NAV Jet Remote Data Source - Users' Guide

Related Articles...

Overview

If your Dynamics NAV resides on a different network domain than does your installation of Microsoft Excel, System Administrators can use the JRDS Admin Guide to help them configure the Jet Remote Data Service.

Once a that service is set-up, users of the Jet Excel add-in can configure a data source to use the service.

Configuring the Data Source Connection

The first step in the Jet add-in is to create a new data source of the type Dynamics NAV 2013 - 2018 with a connection type of Remote Data Service .  Next, the authentication needs to be configured. These options are the same credentials that are used to access NAV.

The user can authenticate against the JRDS using any one of the following:

  1. Their own Windows credentials (this usually only applies to demo environments)
  2. Another user's Windows credentials (e.g., a user on a different domain - usually the domain where the data resides)
  3. NAV User Password credentials.

You will need to contact your system administration to obtain the exact settings being used in your organization.

In this example, Windows authentication is selected for a user account on a separate domain.

To create a new data source connection to your NAV database, start by selecting Settings > Data Source Settings from the Jet ribbon.

  1. On the Data Source Settings window, click the Add button. When the Add Data Source dialog will appear, provide a unique name for our NAV data source, select Dynamics NAV 2013 - 2018 for the Database Type , and Remote Data Service for the Connection Method.

  2. It is expected that users will be provide with a domain name, user name, and password to use for authentication - the same authentication information used to connect to the NAV Role-Tailored Client (RTC) or Web Client.

    auth_tab.png

  3. The connection information for the instance of the JRDS must be configured:

    connection_tab.png

  4. Note that the S erver is the one which is hosting IIS and the JRDS.  The Port is the one which was entered into PowerShell when the Application Container was created.  The Instance is the name entered into PowerShell when the Service Instance was created.

    The dropdown to select the company will populate when opened if the settings are correct.

    All remaining settings are typical of other NAV data source types.  Be sure to select the desired Drilldown type and, in the case or RTC drilldown, the directory where the RTC is installed.

  5. Once the Data Source Settings are correct, you can test them by clicking the Test Connection button at the top of the Data Source Settings window and should see the Test Connection Succeeded message. If there are any issues, the message should help you in troubleshooting.

When upgrading versions of Jet Excel add-in to a much newer release, ensure that both the Jet Remote Data Service installed on the server and the Jet add-in are on the same version to reduce potential issues.

Related Articles

For an optimal Community experience, Please view on Desktop