Microsoft Dynamics NAV / Business Central Connector

Microsoft Dynamics NAV / Business Central

Additional Documentation

This Connector is based on the Dynamics NAV ADO.NET Provider by CData. For additional help, including Connection String parameters, please see:

As of June 15, 2020, this connector supports MS NAV 2013 and higher.

Establishing a Connection

Connecting to DynamicsNAV

Before the provider can connect with DynamicsNAV, OData services need to be enabled on the server. Once OData Services are enabled, the provider will be able to query any services that are published on the server.

In addition, specify a Url to a valid DynamicsNAV server organization root (e.g. http://myserver:7048/) and a ServerInstance (e.g. DynamicsNAV71). If there is not a Service Default Company for the server, set the Company (e.g. 'CRONUS Canada, Inc.') as well.

In a multitenant installation, specify the tenant Id in Tenant (e.g. 'Cronus1').

Authenticating to DynamicsNAV

To authenticate, set the User and Password properties to valid DynamicsNAV logon credentials or Windows user credentials. Select the appropriate authentication method in AuthScheme.

Auth Schemes

The available authentication schemes are configured in IIS where Dynamics NAV is hosted. In IIS you can select to enable or disable Digest, Basic, Windows, or Anonymous authentication. Please consult with your Dynamics NAV admin to determine which authentication scheme is appropriate for you. Set AuthScheme to one of the following:

  • NEGOTIATE (default) - It is part of the Windows authentication, also known as Kerberos.
  • BASIC - Basic authentication.
  • DIGEST - Digest authentication.
  • NTLM - Part of the Windows authentication.
  • NONE - Anonymous authentication.

Advanced Settings

Customizing the SSL Configuration

By default, the provider attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats to do so.

Connecting Through a Firewall or Proxy

HTTP Proxies

To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.

In addition, to authenticate to an HTTP proxy, set ProxyAuthSchemeProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.

Other Proxies

Set the following properties:

  • To use a proxy-based firewall, set FirewallTypeFirewallServer, and FirewallPort.
  • To tunnel the connection, set FirewallType to TUNNEL.
  • To authenticate, specify FirewallUser and FirewallPassword.
  • To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.

Troubleshooting the Connection

To show provider activity from query execution to network traffic, use Logfile and Verbosity. The examples of common connection errors below show how to use these properties to get more context. Contact the support team for help tracing the source of an error or circumventing a performance issue.

  • Authentication errors: Typically, recording a Logfile at Verbosity 4 is necessary to get full details on an authentication error.
  • Queries time out: A server that takes too long to respond will exceed the provider's client-side timeout. Often, setting the Timeout property to a higher value will avoid a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 will show where the time is being spent.
  • The certificate presented by the server cannot be validated: This error indicates that the provider cannot validate the server's certificate through the chain of trust. If you are using a self-signed certificate, there is only one certificate in the chain.

    To resolve this error, you must verify yourself that the certificate can be trusted and specify to the provider that you trust the certificate. One way you can specify that you trust a certificate is to add the certificate to the trusted system store; another is to set SSLServerCert.

CData ADO.NET Provider for Dynamics NAV 2019 - Build 19.0.7354



Dynamics NAV Connection Edit Screen

    • Related Articles

    • Microsoft Dynamics ERP - AX Connector

      Our Microsoft Dynamics AX Connector is no longer supported.  We will offer support for Microsoft Dynamics 365 Finance and Operations in the near future. Parameter Description Domain Object Server Dynamics AX Connection Edit Screen
    • Microsoft Dynamics ERP - GP Connector

      Additional Documentation  This Connector is based on the Dynamics GPADO.NET Provider by CData. For additional help, including String parameters, please see: Dynamics GP Version Support The provider supports read ...
    • Microsoft Dynamics CRM Connector

      Versions of MS CRM Supported: On-Prem v2011 and later, MS CRM Cloud Parameter Description URL After logging into Dynamics CRM, this is the first portion of the URL that displays in your browser's address bar. If your account is hosted by Dynamics ...
    • Microsoft SQL Server Connector

      Overview The "SQL Server" Connector pulls data from Microsoft SQL Server. Using rowversion fields Many integrations run frequently and only want to pick up records modified since the last time the integration ran. This can be accomplished with ...
    • Sage 100 ERP Connector

      Overview Sage 100 versions supported: 2014 and higher. The StarfishETL Sage 100 Connector accesses Sage 100 via web services. It can be used with StarfishETL Windows or the Starfish Ray. If you are using the StarfishETL Windows module you will do all ...