Sign Up for Training |
insightsoftware Company Site
Submit a Request
Become a Jet Insider
Give Feedback

Configure a Native NAV Project in the Jet Data Manager


This article details the steps required to properly configure the Jet Data Manager to work with a Native NAV database.


Before you begin configuring Jet Analytics to work with your Native NAV database, make sure you have the appropriate Open Database connectivity (ODBC) driver installed on the same machine where you have installed the Jet Data Manager. The ODBC driver needs to match your NAV version. You can find the driver on the NAV installation media under the NODBC folder.

You must have the NAV Adapter objects imported and processed in your NAV database before configuring the ODBC connection.

Creating an ODBC Connection

  1. Open the Control Panel, navigate to Administrative Tools Data Sources (ODBC), click on the System DSN tab and click Add.

    The Create New Data Source dialog opens:


    The NODBC driver is a 32-bit application. To run the 32-bit ODBC on a computer that is running a 64-bit version of Windows, run the following command:

    • > Drive:\%systemroot%\SysWOW64\odbcad32.exe
  2. From the list of drivers, you need to find the Microsoft Navision Driver that matches your Native NAV database version.  Click Finish once the proper driver has been selected.


  3. In the Navision ODBC Setup window, first type in the name for this ODBC connection.

  4. Then select, if you are either connecting to a local database (you will need to select a Native NAV database file) or to a server (you will need to type in the Server Name and select the correct Net Type).

  5. Before you can choose the company, type in the User ID and Password or check the check box to use Windows Login instead.  Click the Import License button and browse to your NAV license file.

  6. Click on the Options button and set the following three settings:

    • Identifiers : All Characters
    • Language : Neutral
    • Option Field Type : Integer
  7. Click OK to save the connection and OK again to close the ODBC window.

Configure the Jet Data Manager

You will need to install the 32-bit version of the Jet Data Manager since the NODBC driver is a 32-bit application.
  1. Open Jet Data Manager and either download a new NAV project or open your existing one, that you want to convert to use Native NAV database.

  2. Expand Data Sources at the very bottom and right click NAV data source.  Select Change to Native Provider .


  3. Type in the name (default: NAV) for this data source and select the Use Project Settings radio button.  From the Template System drop down menu you should be able to select your previously created ODBC connection.

    If you encounter a warning message once you select your ODBC connection, click Yes.

    Your company will pop up in the grid view. Check the Manual DSN next to it, and select your previously created ODBC connection from the System DSN drop down menu.

  4. Below the grid, make sure to select the appropriate preset settings. The preset settings need to match your NAV database version (only major version is important, service packs and hot fixes are irrelevant).

  5. Click OK to save and close Navision Native ODBC Source.


  6. After the connection has been configured, you need to set up the accounts.  Right click on NAV data source and select Set up accounts.  Same as with NAV on SQL Server, check the check boxes for all the companies you would like to import to Jet Analytics.

  7. Once the companies have been selected, you can go back into the NAV Native ODBC Source window in the screenshot above and click the Create DSN's button to create DSN connections for the companies specified in Step 6.

  8. The last step is to synchronize NAV objects with the Jet Data Manager.  Right click on NAV data source and select Enhancements Navision Enhancements Settings.  Delete all the Invalid Identifiers and click OK .



  9. Right click NAV data source and select Synchronize Objects.  Once the synchronization process has completed you can go ahead and deploy and execute the entire project.


Was this article helpful?
0 out of 0 found this helpful