![]() |
VOOZH | about |
This article shows how to use the CData JDBC Driver for Dynamics NAV to integrate with the External SQL Sources (ESS) feature in FileMaker Pro, which allows you to link records in FileMaker Pro with related records in your other operational data stores.
You will use the MySQL Remoting feature to access Dynamics NAV as a remote MySQL database. The CData JDBC Driver for Dynamics NAV implements both the JDBC and MySQL standards to integrate with applications like FileMaker Pro that support connections to traditional databases like MySQL but not generic JDBC connections.
There are two data access modes in FileMaker Pro:
The JDBC driver is part of a data access chain. Compared to a native ODBC integration, FileMaker Pro integrations that use MySQL remoting have several additional components. This article shows how to link each of the following components with FileMaker Pro:
On Windows, FileMaker Pro requires the official MySQL driver, the MySQL Connector\ODBC (currently, the best option is Connector\ODBC 8.0.11).
On macOS, FileMaker Pro requires the Actual Technologies Open Databases ODBC driver.
An ODBC driver manager.
On Windows, the driver manager is built in. On macOS, you will need to install a driver manager before installing the ODBC driver; install the iODBC driver manager.
Follow the steps below to enable the MySQL Remoting feature:
Open Terminal and change to the lib subfolder in the installation folder.
$ cd "/Applications/CData/CData JDBC Driver for Dynamics NAV/lib"
dynamicsnav = "http://myserver:7048;User=myserver\Administrator;Password=admin;ServerInstance=DYNAMICSNAV71;"
Before you can connect, OData Services will need to be enabled on the server. Once OData Services are enabled, you will be able to query any Services that are published on the server.
The User and Password properties, under the Authentication section, must be set to valid Dynamics NAV user credentials. In addition, specify a URL to a valid Dynamics NAV server organization root and a ServerInstance. If there is not a Service Default Company for the server, set the Company as well.
See the help documentation for more information about the available connection properties and other configuration options for remoting.
Start the MySQL daemon by specifying the configuration file or settings on the command line. The example below uses the included sample configuration file.
$ java -jar cdata.jdbc.dynamicsnav.jar -f "cdata.jdbc.dynamicsnav.remoting.ini"
After connecting successfully to Dynamics NAV and starting the MySQL daemon, create a MySQL ODBC data source. When working with ODBC data sources, you specify connection properties in a DSN (data source name).
If you have not already obtained an ODBC driver and driver manager, refer to "Outlining the ESS Setup" to determine the components supported for your platform.
Follow the steps below to use the iODBC graphical administrator tool:
You can use the built-in Microsoft ODBC Data Source Administrator to create the ODBC DSN.
Shadow tables exist in an external SQL source but can be used in much the same way as other tables in your FileMaker database; you can add them in the relationships graph, browse data, and create layouts on them.
After specifying the username and password for the DSN, you can add Dynamics NAV tables to the relationships graph. You can now scroll through, sort, edit, and summarize Dynamics NAV data by clicking View -> Browse Mode, just as you would a remote MySQL database.
👁 Tables to be linked to the external data source in the relationships graph. (Salesforce is shown.)Download a free trial of the Dynamics NAV Driver to get started:
Download NowLearn more:
👁 Dynamics NAV IconRapidly create and deploy powerful Java applications that integrate with Dynamics NAV account data including Items, Sales Orders, Purchase Orders, and more!