Sign Up for Training |
Jet Global Company Site
Community
Downloads
Submit a Request
Give Feedback

Creating a Dynamics NAV 2013 and higher - SQL Server Data Source with Jet Reports


Applies to Jet Reports versions 2013 Update 1 and higher

Related Articles...

Overview

Jet Reports includes a data source type for Dynamics NAV 2013 and later (SQL Server).

Jet Reports 2015 Update 1 and higher Jet 2013 Update 1 - 2015 Update 1 (original)
connection_types_c.png

For organizations and users with direct access to the SQL Server on which their NAV 2013 (or later) database is stored, this data source can provide substantially faster reporting access than is traditionally possible through NAV's Web Services.

 

How-To Video

 
Setting up a SQL Server Connection for Dynamics NAV

This video will be a step by step overview of Setting up a NAV Data Source using a SQL Server connection (For NAV 2013 and higher)

General Requirements

  1. You must be using Jet Reports 2013 Update 1 or higher
  2. You must be using Dynamics NAV 2013 or later

    and have access to your NAV SQL database (either this database is on-premises or your hosting provider is willing to allow you to connect directly to the SQL database). 

    If you need to connect to a remote database and do *not* have direct access, you may be able to use the Jet Remote Data Service.
  3. You must be using Windows Authentication or NAV User/Password Authentication

    to access your NAV system. 

    Use of NAV User/Password Authentication requires Jet Reports 2015 Update 1 or higher.

Configuration Settings

  1. Authentication Tab

    Once you have created a new NAV SQL Server data source, the first thing you must do is specify the account information that will be used to connect directly to the SQL Server

    Depending on which version of the Jet Excel add-in you use, you have multiple options:

    Jet version 2015 Update 1 and higher Jet version 2015 Jet version 2013-2013U1

    NAV2013sql_2_2019sml.png

    If your SQL Server is configured to automatically recognize the user names used to log on to Windows, you can use one of the "Windows Authentication" options (either the current Windows user or another Windows user). 

    If your SQL Server is not configured to recognize Windows user names, you will need to choose SQL Server Authentication and provide the user name and password for an account that doeshave permissions to access the SQL Server.  Please contact your system administrator to determine what information should be used. 

    Once you have specified how to access the SQL database, you will then want to specify which NAV user will be used when determining the roles and permissions used to access the NAV data.  If your NAV system is configured to recognize the user names used to log on to Windows, you can choose to use the current Windows users.  Otherwise, versions AFTER 2015 Update 1 also supports the use of NAV User Password authentication  (see information about NAV Authentication types )

    If your SQL Server is configured to automatically recognize the user names used to log on to Windows, you can use one of the Windows Authentication options (either the current Windows user or another Windows user). 

    If your SQL Server is not configured to recognize Windows user names, you will need to choose SQL Server Authentication and provide the user name and password for an account that does have permissions to access the SQL Server.  Please contact your system administrator to determine what information should be used. 

    Note: Regardless of whether you use "SQL Server Authentication" or one of the "Windows Authentication" methods to access your SQL Server, the NAV roles and permissions that are used to access your NAV data are based on the current Windows user name.

    If your SQL Server is configured to automatically recognize the user name you use to log on to your computer, you can use the Windows Authentication option. 

    If your SQL Server is not configured to recognize Windows user names, you will need to choose SQL Server Authentication and provide the user name and password for an account that does have permissions to access the SQL Server.  Please contact your system administrator to determine what information should be used. 

    Note: Regardless of whether you use "Windows Authentication" or "SQL Server Authentication" to access your SQL Server, the NAV roles and permissions that are used to access your NAV data are based on your Windows user name.
  2. Connection Tab

    You will need to provide the name or IP address of the SQL server where your NAV database resides: 

    NAV2013sql_3b.png

    Once this information is provided, you can click the Database down arrow to select the name of your NAV database:

    Next,  click the Company down arrow to select the NAV company name ( this must be specified even if you have only one company in your NAV database):

  3. Test the Connection

    After you have completed these steps, you can click the Test Connection button at the top of the window to ensure that all settings are correct.


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments