Dynamics NAV

1 Connecting to Dynamics NAV

Before the provider can connect with Dynamics NAV, 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 Dynamics NAV 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').

2 Authenticating to Dynamics NAV

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

3 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.

The following are the connection properties for Dynamics NAV. Not all properties are required. Enter only property values pertaining to your installation. Several properties will be automatically initialized with the appRules defaults.

Last updated