# mulesoft Microsoft Dynamics NAV Connector - Full Documentation

<!-- document id=9ad4b84b94510305ed3d737e82c1a223cfda1a49b6f79bd6edec4e5ada14b653 url=/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/index.md -->

---
product: Microsoft Dynamics NAV Connector
version: 3.0
---

# Microsoft Dynamics NAV Connector 3.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Microsoft Dynamics NAV (NAV Connector) enables Mule apps to interact with
Microsoft Dynamics NAV Web Services. Microsoft Dynamics NAV is a global enterprise resource planning
(ERP) solution to assist with finance, manufacturing, customer relationship management, supply
chains, analytics, and electronic commerce for small and medium-sized enterprise and local
subsidiaries of large international groups.

The versions of Microsoft Dynamics NAV supported by this connector are:

- 2013 R2

- 2015

- 2016

- 2017

Release Notes:
[Microsoft Dynamics NAV Connector Release Notes](https://docs.mulesoft.com/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4)  
Exchange:
[Microsoft Dynamics NAV Connector](https://www.mulesoft.com/exchange/com.mulesoft.connectors/mule-microsoft-dynamics-nav-connector/)

## Before You Begin

To use this information, you should be familiar with Microsoft Dynamics NAV, Mule runtime engine
(Mule), Anypoint Connectors, Anypoint Studio, Mule concepts, elements in a Mule flow, and Global
Elements.

You need login credentials to test your connection to your target resource.

For hardware and software requirements and compatibility information, see the Connector Release
Notes.

To use this connector with Maven, view the pom.xml dependency information in the Dependency Snippets
in Anypoint Exchange.

## POM File Information

```xml
<dependency>
  <groupId>com.mulesoft.connectors</groupId>
  <artifactId>mule-microsoft-dynamics-nav-connector</artifactId>
  <version>x.x.x</version>
  <classifier>mule-plugin</classifier>
</dependency>
```

Replace `x.x.x` with the version that corresponds to the connector you are using.

To obtain the most up-to-date `pom.xml` file information, access the connector in
[Anypoint Exchange](https://www.mulesoft.com/exchange/) and click **Dependency Snippets**.

## Primary Use Cases

The Microsoft Dynamics NAV Connector supports these operations:

<table><colgroup><col> <col></colgroup><thead><tr><th>Operation</th><th>Description</th></tr></thead><tbody><tr><td><p>Page Operation</p></td><td><p>Execute one of the operations defined in published Page SOAP services.</p></td></tr><tr><td><p>Codeunit Operation</p></td><td><p>Execute one of the operations defined in published Codeunit SOAP services.</p></td></tr><tr><td><p>OData Query</p></td><td><p>Execute a Query against one of the NAV entities using the OData endpoint.</p></td></tr></tbody></table>

## Getting Started

Before creating a sample flow, a published Page Service is necessary. See below.

## Connect in Anypoint Studio

You can use this connector in Anypoint Studio by first downloading it from Exchange and configuring
it as needed.

## Add the Connector to a Studio Project

Anypoint Studio provides two ways to add the connector to your Studio project: from the Exchange
button in the Studio taskbar or from the Mule Palette view.

### Add the Connector Using Exchange

1.  In Studio, create a Mule project.

2.  Click the Exchange icon **(X)** in the upper-left of the Studio task bar.

3.  In Exchange, click **Login** and supply your Anypoint Platform username and password.

4.  In Exchange, search for "nav".

5.  Select the connector and click **Add to project**.

6.  Follow the prompts to install the connector.

### Add the Connector in Studio

1.  In Studio, create a Mule project.

2.  In the Mule Palette view, click **(X) Search in Exchange**.

3.  In **Add Modules to Project**, type "nav" in the search field.

4.  Click this connector’s name in **Available modules**.

5.  Click **Add**.

6.  Click **Finish**.

### Configure in Studio

1.  Drag an HTTP Listener to the Studio Canvas.

    ![Listener dragged to canvas](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/_images/ms-dynamics-nav-listener-anypoint.png)

    1.  Set the Path.

    2.  Click the green plus sign to configure the listener.

2.  Drag a Dynamics Nav operation to the Studio Canvas.

3.  Click the green plus sign to add a configuration for the connector.

4.  Complete these fields.

    <table><colgroup><col> <col></colgroup><thead><tr><th>Parameter</th><th>Description</th></tr></thead><tbody><tr><td><p>Domain</p></td><td><p>Domain of the Dynamics NAV instance.</p></td></tr><tr><td><p>Username</p></td><td><p>The Windows username to connect to Dynamics NAV.</p></td></tr><tr><td><p>Password</p></td><td><p>The password for the user to connect to Dynamics NAV.</p></td></tr><tr><td><p>SOAP URL</p></td><td><p>Base URL where the SOAP services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/WS</code>. Example: <code>https://hostname:7047/DynamicsNAV90/WS</code></p></td></tr><tr><td><p>OData URL</p></td><td><p>Base URL where the OData services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/OData</code>. Example: <code>https://hostname:7048/DynamicsNAV90/OData</code></p></td></tr><tr><td><p>Company Name (Optional)</p></td><td><p>Dynamics NAV Company to which connect. In case the field is left blank, the default configured one is used.</p></td></tr><tr><td><p>Disable Cn Check</p></td><td><p>For HTTPS certificates, if the certificate is not signed by a trusted partner, the server might respond with an Exception. To prevent this it is possible to disable the CN (Common Name) check. Note: this is not recommended for production environments.</p></td></tr></tbody></table>

5.  Click OK

6.  Configure these fields:

    ![Dynamics NAV Connector config panel on General tab](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/_images/ms-dynamics-nav-op-config.png)

    - Query: The query that to run on Dynamics Nav.

    - Fetch Size: Number of items retrieved on one page.

## Use Case: Studio

![Query flow](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/_images/ms-dynamics-nav-flow.png)

## USe Case: XML

```xml
<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
xmlns:nav="http://www.mulesoft.org/schema/mule/nav"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns="http://www.mulesoft.org/schema/mule/core"
    xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
    http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http
http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/nav
http://www.mulesoft.org/schema/mule/nav/current/mule-nav.xsd
http://www.mulesoft.org/schema/mule/ee/core
http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

	<http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config">
		<http:listener-connection host="localhost" port="8081" />
	</http:listener-config>

	<nav:dynamics-nav-config name="Nav_Connector_Dynamics_nav_config"
      doc:name="Nav Connector Dynamics nav config">
    		<nav:ntlm-connection
            domain="${config.domain}"
            username="${config.username}"
            password="${config.password}"
            soapUrl="${config.soapUrl}"
            odataUrl="${config.odataUrl}"
            companyName="${config.companyName}"
            disableCnCheck="true" />
    </nav:dynamics-nav-config>

    <flow name="query-flow">
    		<http:listener doc:name="Listener"
            config-ref="HTTP_Listener_config"
            path="/query"/>
    		<nav:odata-query fetchSize="10" doc:name="Odata query"
            config-ref="Nav_Connector_Dynamics_nav_config">
    			<nav:query>dsql: SELECT No FROM SalesOrders LIMIT 5</nav:query>
    		</nav:odata-query>
    		<ee:transform doc:name="Transform Message" >
    			<ee:message >
    				<ee:set-payload ><![CDATA[%dw 2.0
    output application/json
    ---
    payload]]></ee:set-payload>
    			</ee:message>
    		</ee:transform>
    </flow>

</mule>
```

## See Also

- [Published Page Service information](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/3.0/%3Chttps://learn.microsoft.com/en-us/previous-versions/dynamicsnav-2015/dd355316(v=nav.80)?redirectedfrom=MSDN>)

- [Microsoft Dynamics NAV Web Services site](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/3.0/%3Chttps://learn.microsoft.com/en-us/previous-versions/dynamicsnav-2016/dd355036(v=nav.90)?redirectedfrom=MSDN>)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=ca63c6c7a6e0ff289034c43b46db26e0748fe57fc7b89cf6be9eb150ce84c88a url=/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/ms-dynamics-nav-connector-reference.md -->

---
product: Microsoft Dynamics NAV Connector
version: 3.0
---

# Microsoft Dynamics NAV Connector 3.0 Reference

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Release Notes:
[Microsoft Dynamics NAV Connector Release Notes](https://docs.mulesoft.com/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4)

## Limitations

- Microsoft Dynamics NAV Connector isn’t supported in CloudHub 2.0 because the underlying CXF
  library requires a JDK to generate schema classes. To support Microsoft Dynamics NAV Connector in
  CloudHub 2.0, the client must provide SOAP requests in raw XML format instead of using Plain Old
  Java Objects (POJOs). For more information, refer to
  [Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 3.0](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/3.0/ms-dynamics-nav-connector-upgrade-migrate).

## Dynamics Nav Configuration

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Name</p></td><td><p>String</p></td><td><p>The name for this configuration. Connectors reference the configuration with this name.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Connection</p></td><td><div><div><ul><li><p>NTLM</p></li><li><p>OAuth</p></li></ul></div></div></td><td><p>The connection types that can be provided to this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Expiration Policy</p></td><td><div><div><p>ExpirationPolicy</p></div></div></td><td><p>Configures the minimum amount of time that a dynamic configuration instance can remain idle before the runtime considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. The runtime actually purges the instances as it sees fit.</p></td><td></td><td></td></tr></tbody></table>

## NTLM Connection Type

> [!NOTE] The JAXB-XJC external library is required for the NTLM and OAuth connection types for Java
> 8, 11, and 17:
>
> - JAXB-XJC v2.3.2
>
>   - Mule runtime 4.3.0 with Java 8 and 11
>
>   - Mule runtime 4.4.0 with Java 8 and 11
>
> - JAXB-XJC v2.3.9
>
>   - Mule runtime 4.5.0 with Java 8 and 11
>
>   - Mule runtime 4.6.0 with Java 8, 11, and 17

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Domain</p></td><td><div><div><p>String</p></div></div></td><td><p>Domain of the Dynamics NAV instance</p></td><td></td><td></td></tr><tr><td><p>Username</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows username to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Password</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows password to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Soap Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the SOAP services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/WS</code>. Example: <code>https://hostname:7047/DynamicsNAV90/WS</code></p></td><td></td><td><p>x</p></td></tr><tr><td><p>OData Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the OData services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/OData</code>. Example: <code>https://hostname:7048/DynamicsNAV90/OData</code>.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Company Name</p></td><td><div><div><p>String</p></div></div></td><td><p>Dynamics NAV Company to which connect. In case the field is left blank, the default configured one is used.</p></td><td></td><td></td></tr><tr><td><p>Disable SSL certificate validation</p></td><td><div><div><p>Boolean</p></div></div></td><td></td><td><p>false</p></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p>Reconnection</p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy</p></td><td></td><td></td></tr><tr><td><p>Pooling Profile</p></td><td><div><div><p>PoolingProfile</p></div></div></td><td><p>Characteristics of the connection pool</p></td><td></td><td></td></tr></tbody></table>

## OAuth Connection Type

Use OAuth 2.0 to delegate user authentication to the service hosting the user account. For more
information, refer to
[Configuring OAuth 2.0 for Connectors](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2),
[Configuring OAuth 2.0 for Connectors on CloudHub](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2-cloudhub),
or [OAuth Support in the SDK](https://docs.mulesoft.com/mule-sdk/latest/oauth).

> [!NOTE] The JAXB-XJC external library is required for the NTLM and OAuth connection types for Java
> 8, 11, and 17:
>
> - JAXB-XJC v2.3.2
>
>   - Mule runtime 4.3.0 with Java 8 and 11
>
>   - Mule runtime 4.4.0 with Java 8 and 11
>
> - JAXB-XJC v2.3.9
>
>   - Mule runtime 4.5.0 with Java 8 and 11
>
>   - Mule runtime 4.6.0 with Java 8, 11, and 17

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Username</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows username to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Access Token</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows password to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Soap Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the SOAP services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/WS</code>. Example: <code>https://hostname:7047/DynamicsNAV90/WS</code></p></td><td></td><td><p>x</p></td></tr><tr><td><p>OData Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the OData services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/OData</code>. Example: <code>https://hostname:7048/DynamicsNAV90/OData</code>.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Company Name</p></td><td><div><div><p>String</p></div></div></td><td><p>Dynamics NAV Company to which connect. In case the field is left blank, the default configured one is used.</p></td><td></td><td></td></tr><tr><td><p>Disable SSL certificate validation</p></td><td><div><div><p>Boolean</p></div></div></td><td></td><td><p>false</p></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p>Reconnection</p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy</p></td><td></td><td></td></tr><tr><td><p>Pooling Profile</p></td><td><div><div><p>PoolingProfile</p></div></div></td><td><p>Characteristics of the connection pool</p></td><td></td><td></td></tr></tbody></table>

## Associated Operations

- Codeunit Operation

- OData Query

- Page Operation

## Codeunit Operation

`<nav:codeunit-operation>`

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Entity</p></td><td><div><div><p>Object</p></div></div></td><td></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Output Mime Type</p></td><td><div><div><p>String</p></div></div></td><td><p>MIME type of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Output Encoding</p></td><td><div><div><p>String</p></div></div></td><td><p>Encoding of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Service</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Operation</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>The name of a variable on which the operation’s output will be placed</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>An expression that will be evaluated against the operation’s output and the outcome of that expression will be stored in the target variable</p></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p>Reconnect</p></li><li><p>Reconnect Forever</p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr></tbody></table>

### For Configurations

- dynamics-nav-config

### Throws

- NAV:CONNECTIVITY

- NAV:INCORRECT\_CREDENTIALS

- NAV:RETRY\_EXHAUSTED

- NAV:UNKNOWN

## OData Query

`<nav:odata-query>`

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Query</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Fetch Size</p></td><td><div><div><p>Number</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p>Repeatable In Memory Iterable</p></li><li><p>Repeatable File Store Iterable</p></li></ul></div></div></td><td><p>Configure if repeatable streams should be used and their behavior</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>The name of a variable on which the operation’s output will be placed</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>An expression that will be evaluated against the operation’s output and the outcome of that expression will be stored in the target variable</p></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p>Reconnect</p></li><li><p>Reconnect Forever</p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Array of Object</p></td></tr></tbody></table>

### For Configurations

- dynamics-nav-config

### Throws

- NAV:CONNECTIVITY

- NAV:INCORRECT\_CREDENTIALS

- NAV:UNKNOWN

## Page Operation

`<nav:page-operation>`

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Entity</p></td><td><div><div><p>Object</p></div></div></td><td></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Output Mime Type</p></td><td><div><div><p>String</p></div></div></td><td><p>MIME type of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Output Encoding</p></td><td><div><div><p>String</p></div></div></td><td><p>Encoding of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Service</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Operation</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>The name of a variable on which the operation’s output will be placed</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>An expression that will be evaluated against the operation’s output and the outcome of that expression will be stored in the target variable</p></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p>Reconnect</p></li><li><p>Reconnect Forever</p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr></tbody></table>

### For Configurations

- dynamics-nav-config

### Throws

- NAV:CONNECTIVITY

- NAV:INCORRECT\_CREDENTIALS

- NAV:RETRY\_EXHAUSTED

- NAV:UNKNOWN

## Reconnection Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Fails Deployment</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p>Reconnect</p></li><li><p>Reconnect Forever</p></li></ul></div></div></td><td><p>The reconnection strategy to use</p></td><td></td><td></td></tr></tbody></table>

### Reconnect

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often to reconnect (in milliseconds)</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Count</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>The number of reconnection attempts to make</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy runs in a separate, non-blocking thread</p></div></div></td><td><div><div><p>true</p></div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect Forever

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy runs in a separate, non-blocking thread</p></div></div></td><td><div><div><p>true</p></div></div></td><td><div></div></td></tr></tbody></table>

## Pooling Profile Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Max Active</p></td><td><div><div><p>Number</p></div></div></td><td><p>Controls the maximum number of Mule components that can be borrowed from a session at one time. When set to a negative value, there is no limit to the number of components that may be active at one time. When maxActive is exceeded, the pool is said to be exhausted.</p></td><td></td><td></td></tr><tr><td><p>Max Idle</p></td><td><div><div><p>Number</p></div></div></td><td><p>Controls the maximum number of Mule components that can sit idle in the pool at any time. When set to a negative value, there is no limit to the number of Mule components that may be idle at one time.</p></td><td></td><td></td></tr><tr><td><p>Max Wait</p></td><td><div><div><p>Number</p></div></div></td><td><p>Specifies the number of milliseconds to wait for a pooled component to become available when the pool is exhausted and the exhaustedAction is set to WHEN_EXHAUSTED_WAIT.</p></td><td></td><td></td></tr><tr><td><p>Min Eviction Millis</p></td><td><div><div><p>Number</p></div></div></td><td><p>Determines the minimum amount of time an object may sit idle in the pool before it is eligible for eviction. When non-positive, no objects will be evicted from the pool due to idle time alone.</p></td><td></td><td></td></tr><tr><td><p>Eviction Check Interval Millis</p></td><td><div><div><p>Number</p></div></div></td><td><p>Specifies the number of milliseconds between runs of the object evictor. When non-positive, no object evictor is executed.</p></td><td></td><td></td></tr><tr><td><p>Exhausted Action</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>WHEN_EXHAUSTED_GROW</p></li><li><p>WHEN_EXHAUSTED_WAIT</p></li><li><p>WHEN_EXHAUSTED_FAIL</p></li></ul></div></div></td><td><p>Specifies the behavior of the Mule component pool when the pool is exhausted. Possible values are: "WHEN_EXHAUSTED_FAIL", which will throw a NoSuchElementException, "WHEN_EXHAUSTED_WAIT", which will block by invoking Object.wait(long) until a new or idle object is available, or WHEN_EXHAUSTED_GROW, which will create a new Mule instance and return it, essentially making maxActive meaningless. If a positive maxWait value is supplied, it will block for at most that many milliseconds, after which a NoSuchElementException will be thrown. If maxThreadWait is a negative value, it will block indefinitely.</p></td><td></td><td></td></tr><tr><td><p>Initialisation Policy</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>INITIALISE_NONE</p></li><li><p>INITIALISE_ONE</p></li><li><p>INITIALISE_ALL</p></li></ul></div></div></td><td><p>Determines how components in a pool should be initialized. The possible values are: INITIALISE_NONE (will not load any components into the pool on startup), INITIALISE_ONE (will load one initial component into the pool on startup), or INITIALISE_ALL (will load all components in the pool on startup)</p></td><td></td><td></td></tr><tr><td><p>Disabled</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Whether pooling should be disabled</p></td><td></td><td></td></tr></tbody></table>

## Expiration Policy Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Max Idle Time</p></td><td><div><div><p>Number</p></div></div></td><td><p>A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it’s considered eligible for expiration</p></td><td></td><td></td></tr><tr><td><p>Time Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>A time unit that qualifies the maxIdleTime attribute</p></td><td></td><td></td></tr></tbody></table>

### Error Mapping

Error mapping.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Source</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>ANY</p></li><li><p>REDELIVERY_EXHAUSTED</p></li><li><p>TRANSFORMATION</p></li><li><p>EXPRESSION</p></li><li><p>SECURITY</p></li><li><p>CLIENT_SECURITY</p></li><li><p>SERVER_SECURITY</p></li><li><p>ROUTING</p></li><li><p>CONNECTIVITY</p></li><li><p>RETRY_EXHAUSTED</p></li><li><p>TIMEOUT</p></li></ul></div></div></td><td><div><div><p>Source.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Target</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Target.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

## Repeatable In Memory Iterable Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Initial Buffer Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is the amount of instances that will be initially be allowed to be kept in memory in order to consume the stream and provide random access to it. If the stream contains more data than can fit into this buffer, then it will be expanded according to the bufferSizeIncrement attribute, with an upper limit of maxInMemorySize. Default value is 100 instances.</p></td><td></td><td></td></tr><tr><td><p>Buffer Size Increment</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is by how much will the buffer size expands if it exceeds its initial size. Setting a value of zero or lower will mean that the buffer should not expand, meaning that a STREAM_MAXIMUM_SIZE_EXCEEDED error will be raised when the buffer gets full. Default value is 100 instances.</p></td><td></td><td></td></tr><tr><td><p>Max Buffer Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is the maximum amount of memory that will be used. If more than that is used then a STREAM_MAXIMUM_SIZE_EXCEEDED error will be raised. A value lower or equal to zero means no limit.</p></td><td></td><td></td></tr></tbody></table>

## Repeatable File Store Iterable Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Max In Memory Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is the maximum amount of instances that will be kept in memory. If more than that is required, then it will start to buffer the content on disk.</p></td><td></td><td></td></tr><tr><td><p>Buffer Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><p>The unit in which maxInMemorySize is expressed</p></td><td></td><td></td></tr></tbody></table>

## See Also

[Salesforce Help](https://help.salesforce.com)

<!-- document id=d260c38d02c01b213d36c01800e2d50f75e006dd664e0ca77687b3127fcbb9ec url=/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/index.md -->

---
product: Microsoft Dynamics NAV Connector
version: 4.0
is-latest-version: true
---

# Microsoft Dynamics NAV Connector 4.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Microsoft Dynamics NAV (NAV Connector) enables Mule apps to interact with
Microsoft Dynamics NAV Web Services. Microsoft Dynamics NAV is a global enterprise resource planning
(ERP) solution to assist with finance, manufacturing, customer relationship management, supply
chains, analytics, and electronic commerce for small and medium-sized enterprise and local
subsidiaries of large international groups.

The versions of Microsoft Dynamics NAV supported by this connector are:

- 2013 R2

- 2015

- 2016

- 2017

Release Notes:
[Microsoft Dynamics NAV Connector Release Notes](https://docs.mulesoft.com/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4)  
Exchange:
[Microsoft Dynamics NAV Connector](https://www.mulesoft.com/exchange/com.mulesoft.connectors/mule-microsoft-dynamics-nav-connector/)

## Before You Begin

To use this information, you should be familiar with Microsoft Dynamics NAV, Mule runtime engine
(Mule), Anypoint Connectors, Anypoint Studio, Mule concepts, elements in a Mule flow, and Global
Elements.

You need login credentials to test your connection to your target resource.

For hardware and software requirements and compatibility information, see the Connector Release
Notes.

To use this connector with Maven, view the pom.xml dependency information in the Dependency Snippets
in Anypoint Exchange.

## POM File Information

```xml
<dependency>
  <groupId>com.mulesoft.connectors</groupId>
  <artifactId>mule-microsoft-dynamics-nav-connector</artifactId>
  <version>x.x.x</version>
  <classifier>mule-plugin</classifier>
</dependency>
```

Replace `x.x.x` with the version that corresponds to the connector you are using.

To obtain the most up-to-date `pom.xml` file information, access the connector in
[Anypoint Exchange](https://www.mulesoft.com/exchange/) and click **Dependency Snippets**.

## Primary Use Cases

The Microsoft Dynamics NAV Connector supports these operations:

<table><colgroup><col> <col></colgroup><thead><tr><th>Operation</th><th>Description</th></tr></thead><tbody><tr><td><p>Page Operation</p></td><td><p>Execute one of the operations defined in published Page SOAP services.</p></td></tr><tr><td><p>Codeunit Operation</p></td><td><p>Execute one of the operations defined in published Codeunit SOAP services.</p></td></tr><tr><td><p>OData Query</p></td><td><p>Execute a Query against one of the NAV entities using the OData endpoint.</p></td></tr></tbody></table>

## Getting Started

Before creating a sample flow, a published Page Service is necessary. See below.

## Connect in Anypoint Studio

You can use this connector in Anypoint Studio by first downloading it from Exchange and configuring
it as needed.

## Add the Connector to a Studio Project

Anypoint Studio provides two ways to add the connector to your Studio project: from the Exchange
button in the Studio taskbar or from the Mule Palette view.

### Add the Connector Using Exchange

1.  In Studio, create a Mule project.

2.  Click the Exchange icon **(X)** in the upper-left of the Studio task bar.

3.  In Exchange, click **Login** and supply your Anypoint Platform username and password.

4.  In Exchange, search for "nav".

5.  Select the connector and click **Add to project**.

6.  Follow the prompts to install the connector.

### Add the Connector in Studio

1.  In Studio, create a Mule project.

2.  In the Mule Palette view, click **(X) Search in Exchange**.

3.  In **Add Modules to Project**, type "nav" in the search field.

4.  Click this connector’s name in **Available modules**.

5.  Click **Add**.

6.  Click **Finish**.

### Configure in Studio

1.  Drag an HTTP Listener to the Studio Canvas.

    ![Listener dragged to canvas](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/_images/ms-dynamics-nav-listener-anypoint.png)

    1.  Set the Path.

    2.  Click the green plus sign to configure the listener.

2.  Drag a Dynamics Nav operation to the Studio Canvas.

3.  Click the green plus sign to add a configuration for the connector.

4.  Complete these fields.

    <table><colgroup><col> <col></colgroup><thead><tr><th>Parameter</th><th>Description</th></tr></thead><tbody><tr><td><p><strong>Domain</strong></p></td><td><p>Domain of the Dynamics NAV instance.</p></td></tr><tr><td><p><strong>Username</strong></p></td><td><p>The Windows username to connect to Dynamics NAV.</p></td></tr><tr><td><p><strong>Password</strong></p></td><td><p>The Windows password to connect to Dynamics NAV.</p></td></tr><tr><td><p><strong>Soap Url</strong></p></td><td><p>Base URL where the SOAP services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/WS</code>. Example: <code>https://hostname:7047/DynamicsNAV90/WS</code></p></td></tr><tr><td><p><strong>Odata Url</strong></p></td><td><p>Base URL where the OData services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/OData</code>. Example: <code>https://hostname:7048/DynamicsNAV90/OData</code></p></td></tr><tr><td><p><strong>Company Name</strong></p></td><td><p>Dynamics NAV Company to which connect. In case the field is left blank, the default configured one is used.</p></td></tr><tr><td><p><strong>Disable SSL certificate validation</strong></p></td><td><p>For HTTPS certificates, if the certificate isn’t signed by a trusted partner, the server might respond with an exception. You can disable the CN (Common Name) check. This isn’t recommended for production environments.</p></td></tr></tbody></table>

5.  On the **Advanced** tab, set **Response Timeout** and **Response Timeout Unit** if you don’t
    want the defaults. The default response timeout is 5000 milliseconds.

    For more information, see [NTLM Connection Type](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#ntlm) and
    [OAuth Connection Type](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#dynamics-nav-config_oauth).

6.  Click OK.

7.  Configure these fields:

    ![Dynamics NAV Connector config panel on General tab](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/_images/ms-dynamics-nav-op-config.png)

    - **Query**: The query to run on Dynamics NAV.

    - **Fetch Size**: Number of items retrieved on one page.

## Use Case: Studio

![Query flow](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/_images/ms-dynamics-nav-flow.png)

## USe Case: XML

```xml
<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
xmlns:nav="http://www.mulesoft.org/schema/mule/nav"
	xmlns:http="http://www.mulesoft.org/schema/mule/http"
	xmlns="http://www.mulesoft.org/schema/mule/core"
    xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
    http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http
http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/nav
http://www.mulesoft.org/schema/mule/nav/current/mule-nav.xsd
http://www.mulesoft.org/schema/mule/ee/core
http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">

	<http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config">
		<http:listener-connection host="localhost" port="8081" />
	</http:listener-config>

	<nav:dynamics-nav-config name="Nav_Connector_Dynamics_nav_config"
      doc:name="Nav Connector Dynamics nav config">
    		<nav:ntlm-connection
            domain="${config.domain}"
            username="${config.username}"
            password="${config.password}"
            soapUrl="${config.soapUrl}"
            odataUrl="${config.odataUrl}"
            companyName="${config.companyName}"
            disableCnCheck="true" />
    </nav:dynamics-nav-config>

    <flow name="query-flow">
    		<http:listener doc:name="Listener"
            config-ref="HTTP_Listener_config"
            path="/query"/>
    		<nav:odata-query fetchSize="10" doc:name="Odata query"
            config-ref="Nav_Connector_Dynamics_nav_config">
    			<nav:query>dsql: SELECT No FROM SalesOrders LIMIT 5</nav:query>
    		</nav:odata-query>
    		<ee:transform doc:name="Transform Message" >
    			<ee:message >
    				<ee:set-payload ><![CDATA[%dw 2.0
    output application/json
    ---
    payload]]></ee:set-payload>
    			</ee:message>
    		</ee:transform>
    </flow>

</mule>
```

## See Also

- [Published Page Service information](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/%3Chttps://learn.microsoft.com/en-us/previous-versions/dynamicsnav-2015/dd355316(v=nav.80)?redirectedfrom=MSDN>)

- [Microsoft Dynamics NAV Web Services site](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/%3Chttps://learn.microsoft.com/en-us/previous-versions/dynamicsnav-2016/dd355036(v=nav.90)?redirectedfrom=MSDN>)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=325f66fbf6fcd41bb4041391bd17739bd5e6af3bdbda01ba0f71a31f457cf97a url=/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference.md -->

---
product: Microsoft Dynamics NAV Connector
version: 4.0
is-latest-version: true
---

# Microsoft Dynamics NAV Connector 4.0 Reference

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Release Notes:
[Microsoft Dynamics NAV Connector Release Notes](https://docs.mulesoft.com/release-notes/connector/ms-dynamics-nav-connector-release-notes-mule-4)

## Limitations

- Microsoft Dynamics NAV Connector isn’t supported in CloudHub 2.0 because the underlying CXF
  library requires a JDK to generate schema classes. To support Microsoft Dynamics NAV Connector in
  CloudHub 2.0, the client must provide SOAP requests in raw XML format instead of using Plain Old
  Java Objects (POJOs). For more information, refer to
  [Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 4.0](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-upgrade-migrate).

## Dynamics Nav Configuration

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Name</p></td><td><p>String</p></td><td><p>The name for this configuration. Connectors reference the configuration with this name.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Connection</p></td><td><div><div><ul><li><p>NTLM</p></li><li><p>OAuth</p></li></ul></div></div></td><td><p>The connection types that can be provided to this configuration.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Expiration Policy</p></td><td><div><div><p><a href="#ExpirationPolicy">Expiration Policy Type</a></p></div></div></td><td><p>Configures the minimum amount of time that a dynamic configuration instance can remain idle before the runtime considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. The runtime actually purges the instances as it sees fit.</p></td><td></td><td></td></tr></tbody></table>

## NTLM Connection Type

> [!NOTE] The JAXB-XJC external library is required for the NTLM and OAuth connection types:
>
> - `org.glassfish.jaxb:jaxb-xjc:4.0.9`
>
>   - Mule runtime 4.9.0 and later with Java 17

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Domain</p></td><td><div><div><p>String</p></div></div></td><td><p>Domain of the Dynamics NAV instance</p></td><td></td><td></td></tr><tr><td><p>Username</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows username to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Password</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows password to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Soap Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the SOAP services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/WS</code>. Example: <code>https://hostname:7047/DynamicsNAV90/WS</code></p></td><td></td><td><p>x</p></td></tr><tr><td><p>Odata Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the OData services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/OData</code>. Example: <code>https://hostname:7048/DynamicsNAV90/OData</code>.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Company Name</p></td><td><div><div><p>String</p></div></div></td><td><p>Dynamics NAV Company to which connect. In case the field is left blank, the default configured one is used.</p></td><td></td><td></td></tr><tr><td><p>Disable SSL certificate validation</p></td><td><div><div><p>Boolean</p></div></div></td><td></td><td><p>false</p></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>HTTP response timeout. This field is on the Advanced tab. Expressions aren’t supported.</p></td><td><p>5000</p></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the response timeout. This field is on the Advanced tab. Expressions aren’t supported.</p></td><td><p>MILLISECONDS</p></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection Type</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy</p></td><td></td><td></td></tr><tr><td><p>Pooling Profile</p></td><td><div><div><p><a href="#PoolingProfile">Pooling Profile Type</a></p></div></div></td><td><p>Characteristics of the connection pool</p></td><td></td><td></td></tr></tbody></table>

## OAuth Connection Type

Use OAuth 2.0 to delegate user authentication to the service hosting the user account. For more
information, refer to
[Configuring OAuth 2.0 for Connectors](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2),
[Configuring OAuth 2.0 for Connectors on CloudHub](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2-cloudhub),
or [OAuth Support in the SDK](https://docs.mulesoft.com/mule-sdk/latest/oauth).

> [!NOTE] The JAXB-XJC external library is required for the NTLM and OAuth connection types:
>
> - `org.glassfish.jaxb:jaxb-xjc:4.0.9`
>
>   - Mule runtime 4.9.0 and later with Java 17

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Username</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows username to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Access Token</p></td><td><div><div><p>String</p></div></div></td><td><p>The Windows password to connect to Dynamics NAV</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Soap Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the SOAP services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/WS</code>. Example: <code>https://hostname:7047/DynamicsNAV90/WS</code></p></td><td></td><td><p>x</p></td></tr><tr><td><p>Odata Url</p></td><td><div><div><p>String</p></div></div></td><td><p>Base URL where the OData services are exposed in the form <code>https://&lt;Server&gt;:&lt;WebServicePort&gt;/&lt;ServerInstance&gt;/OData</code>. Example: <code>https://hostname:7048/DynamicsNAV90/OData</code>.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Company Name</p></td><td><div><div><p>String</p></div></div></td><td><p>Dynamics NAV Company to which connect. In case the field is left blank, the default configured one is used.</p></td><td></td><td></td></tr><tr><td><p>Disable SSL certificate validation</p></td><td><div><div><p>Boolean</p></div></div></td><td></td><td><p>false</p></td><td></td></tr><tr><td><p>Response Timeout</p></td><td><div><div><p>Number</p></div></div></td><td><p>HTTP response timeout. This field is on the Advanced tab. Expressions aren’t supported.</p></td><td><p>5000</p></td><td></td></tr><tr><td><p>Response Timeout Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>Time unit for the response timeout. This field is on the Advanced tab. Expressions aren’t supported.</p></td><td><p>MILLISECONDS</p></td><td></td></tr><tr><td><p>Reconnection</p></td><td><div><div><p><a href="#Reconnection">Reconnection Type</a></p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy</p></td><td></td><td></td></tr><tr><td><p>Pooling Profile</p></td><td><div><div><p><a href="#PoolingProfile">Pooling Profile Type</a></p></div></div></td><td><p>Characteristics of the connection pool</p></td><td></td><td></td></tr></tbody></table>

## Associated Operations

- [Codeunit Operation](#codeunitOperation)

- [OData Query](#odataQuery)

- [Page Operation](#pageOperation)

## Codeunit Operation

`<nav:codeunit-operation>`

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Entity</p></td><td><div><div><p>Object</p></div></div></td><td></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Output Mime Type</p></td><td><div><div><p>String</p></div></div></td><td><p>MIME type of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Output Encoding</p></td><td><div><div><p>String</p></div></div></td><td><p>Encoding of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Service</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Operation</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>The name of a variable on which the operation’s output will be placed</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>An expression that will be evaluated against the operation’s output and the outcome of that expression will be stored in the target variable</p></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#reconnect">Reconnect</a></p></li><li><p><a href="#reconnect-forever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr></tbody></table>

### For Configurations

- [Dynamics Nav Configuration](#dynamics-nav-config)

### Throws

- NAV:CONNECTIVITY

- NAV:INCORRECT\_CREDENTIALS

- NAV:RETRY\_EXHAUSTED

## OData Query

`<nav:odata-query>`

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Query</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Fetch Size</p></td><td><div><div><p>Number</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Streaming Strategy</p></td><td><div><div><ul><li><p><a href="#repeatable-in-memory-iterable">Repeatable In Memory Iterable Type</a></p></li><li><p><a href="#repeatable-file-store-iterable">Repeatable File Store Iterable Type</a></p></li></ul></div></div></td><td><p>Configure if repeatable streams should be used and their behavior</p></td><td></td><td></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>The name of a variable on which the operation’s output will be placed</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>An expression that will be evaluated against the operation’s output and the outcome of that expression will be stored in the target variable</p></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#reconnect">Reconnect</a></p></li><li><p><a href="#reconnect-forever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Array of Object</p></td></tr></tbody></table>

### For Configurations

- [Dynamics Nav Configuration](#dynamics-nav-config)

### Throws

- NAV:CONNECTIVITY

- NAV:INCORRECT\_CREDENTIALS

- NAV:RETRY\_EXHAUSTED

## Page Operation

`<nav:page-operation>`

### Parameters

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Name</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Configuration</p></td><td><p>String</p></td><td><p>The name of the configuration to use.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Entity</p></td><td><div><div><p>Object</p></div></div></td><td></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Output Mime Type</p></td><td><div><div><p>String</p></div></div></td><td><p>MIME type of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Output Encoding</p></td><td><div><div><p>String</p></div></div></td><td><p>Encoding of the payload that this operation outputs.</p></td><td></td><td></td></tr><tr><td><p>Config Ref</p></td><td><div><div><p>ConfigurationProvider</p></div></div></td><td><p>Name of the configuration to use to execute this component.</p></td><td></td><td><p>x</p></td></tr><tr><td><p>Service</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Operation</p></td><td><div><div><p>String</p></div></div></td><td></td><td></td><td><p>x</p></td></tr><tr><td><p>Target Variable</p></td><td><div><div><p>String</p></div></div></td><td><p>The name of a variable on which the operation’s output will be placed</p></td><td></td><td></td></tr><tr><td><p>Target Value</p></td><td><div><div><p>String</p></div></div></td><td><p>An expression that will be evaluated against the operation’s output and the outcome of that expression will be stored in the target variable</p></td><td><p><code>#[payload]</code></p></td><td></td></tr><tr><td><p>Error Mappings</p></td><td><div><div><p>Array of <a href="#ErrorMapping">Error Mapping</a></p></div></div></td><td><p>Set of error mappings.</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#reconnect">Reconnect</a></p></li><li><p><a href="#reconnect-forever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>A retry strategy in case of connectivity errors</p></td><td></td><td></td></tr></tbody></table>

### Output

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Type</p></td><td><p>Any</p></td></tr></tbody></table>

### For Configurations

- [Dynamics Nav Configuration](#dynamics-nav-config)

### Throws

- NAV:CONNECTIVITY

- NAV:INCORRECT\_CREDENTIALS

- NAV:RETRY\_EXHAUSTED

## Reconnection Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Fails Deployment</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test doesn’t pass after exhausting the associated reconnection strategy</p></td><td></td><td></td></tr><tr><td><p>Reconnection Strategy</p></td><td><div><div><ul><li><p><a href="#reconnect">Reconnect</a></p></li><li><p><a href="#reconnect-forever">Reconnect Forever</a></p></li></ul></div></div></td><td><p>The reconnection strategy to use</p></td><td></td><td></td></tr></tbody></table>

### Reconnect

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often to reconnect (in milliseconds)</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Count</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>The number of reconnection attempts to make</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy runs in a separate, non-blocking thread</p></div></div></td><td><div><div><p>true</p></div></div></td><td><div></div></td></tr></tbody></table>

### Reconnect Forever

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Frequency</strong></p></td><td><div><div><p>Number</p></div></div></td><td><div><div><p>How often in milliseconds to reconnect</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>blocking</strong></p></td><td><div><div><p>Boolean</p></div></div></td><td><div><div><p>If false, the reconnection strategy runs in a separate, non-blocking thread</p></div></div></td><td><div><div><p>true</p></div></div></td><td><div></div></td></tr></tbody></table>

## Pooling Profile Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Max Active</p></td><td><div><div><p>Number</p></div></div></td><td><p>Controls the maximum number of Mule components that can be borrowed from a session at one time. When set to a negative value, there is no limit to the number of components that may be active at one time. When maxActive is exceeded, the pool is said to be exhausted.</p></td><td></td><td></td></tr><tr><td><p>Max Idle</p></td><td><div><div><p>Number</p></div></div></td><td><p>Controls the maximum number of Mule components that can sit idle in the pool at any time. When set to a negative value, there is no limit to the number of Mule components that may be idle at one time.</p></td><td></td><td></td></tr><tr><td><p>Max Wait</p></td><td><div><div><p>Number</p></div></div></td><td><p>Specifies the number of milliseconds to wait for a pooled component to become available when the pool is exhausted and the exhaustedAction is set to WHEN_EXHAUSTED_WAIT.</p></td><td></td><td></td></tr><tr><td><p>Min Eviction Millis</p></td><td><div><div><p>Number</p></div></div></td><td><p>Determines the minimum amount of time an object may sit idle in the pool before it is eligible for eviction. When non-positive, no objects will be evicted from the pool due to idle time alone.</p></td><td></td><td></td></tr><tr><td><p>Eviction Check Interval Millis</p></td><td><div><div><p>Number</p></div></div></td><td><p>Specifies the number of milliseconds between runs of the object evictor. When non-positive, no object evictor is executed.</p></td><td></td><td></td></tr><tr><td><p>Exhausted Action</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>WHEN_EXHAUSTED_GROW</p></li><li><p>WHEN_EXHAUSTED_WAIT</p></li><li><p>WHEN_EXHAUSTED_FAIL</p></li></ul></div></div></td><td><p>Specifies the behavior of the Mule component pool when the pool is exhausted. Possible values are: "WHEN_EXHAUSTED_FAIL", which will throw a NoSuchElementException, "WHEN_EXHAUSTED_WAIT", which will block by invoking Object.wait(long) until a new or idle object is available, or WHEN_EXHAUSTED_GROW, which will create a new Mule instance and return it, essentially making maxActive meaningless. If a positive maxWait value is supplied, it will block for at most that many milliseconds, after which a NoSuchElementException will be thrown. If maxThreadWait is a negative value, it will block indefinitely.</p></td><td></td><td></td></tr><tr><td><p>Initialisation Policy</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>INITIALISE_NONE</p></li><li><p>INITIALISE_ONE</p></li><li><p>INITIALISE_ALL</p></li></ul></div></div></td><td><p>Determines how components in a pool should be initialized. The possible values are: INITIALISE_NONE (will not load any components into the pool on startup), INITIALISE_ONE (will load one initial component into the pool on startup), or INITIALISE_ALL (will load all components in the pool on startup)</p></td><td></td><td></td></tr><tr><td><p>Disabled</p></td><td><div><div><p>Boolean</p></div></div></td><td><p>Whether pooling should be disabled</p></td><td></td><td></td></tr></tbody></table>

## Expiration Policy Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Max Idle Time</p></td><td><div><div><p>Number</p></div></div></td><td><p>A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it’s considered eligible for expiration</p></td><td></td><td></td></tr><tr><td><p>Time Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>NANOSECONDS</p></li><li><p>MICROSECONDS</p></li><li><p>MILLISECONDS</p></li><li><p>SECONDS</p></li><li><p>MINUTES</p></li><li><p>HOURS</p></li><li><p>DAYS</p></li></ul></div></div></td><td><p>A time unit that qualifies the maxIdleTime attribute</p></td><td></td><td></td></tr></tbody></table>

### Error Mapping

Error mapping.

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p><strong>Source</strong></p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>ANY</p></li><li><p>REDELIVERY_EXHAUSTED</p></li><li><p>TRANSFORMATION</p></li><li><p>EXPRESSION</p></li><li><p>SECURITY</p></li><li><p>CLIENT_SECURITY</p></li><li><p>SERVER_SECURITY</p></li><li><p>ROUTING</p></li><li><p>CONNECTIVITY</p></li><li><p>RETRY_EXHAUSTED</p></li><li><p>TIMEOUT</p></li></ul></div></div></td><td><div><div><p>Source.</p></div></div></td><td><div></div></td><td><div></div></td></tr><tr><td><p><strong>Target</strong></p></td><td><div><div><p>String</p></div></div></td><td><div><div><p>Target.</p></div></div></td><td><div></div></td><td><div><div><p>x</p></div></div></td></tr></tbody></table>

## Repeatable In Memory Iterable Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Initial Buffer Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is the amount of instances that will be initially be allowed to be kept in memory in order to consume the stream and provide random access to it. If the stream contains more data than can fit into this buffer, then it will be expanded according to the bufferSizeIncrement attribute, with an upper limit of maxInMemorySize. Default value is 100 instances.</p></td><td></td><td></td></tr><tr><td><p>Buffer Size Increment</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is by how much will the buffer size expands if it exceeds its initial size. Setting a value of zero or lower will mean that the buffer should not expand, meaning that a STREAM_MAXIMUM_SIZE_EXCEEDED error will be raised when the buffer gets full. Default value is 100 instances.</p></td><td></td><td></td></tr><tr><td><p>Max Buffer Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is the maximum amount of memory that will be used. If more than that is used then a STREAM_MAXIMUM_SIZE_EXCEEDED error will be raised. A value lower or equal to zero means no limit.</p></td><td></td><td></td></tr></tbody></table>

## Repeatable File Store Iterable Type

<table><colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Field</th><th>Type</th><th>Description</th><th>Default Value</th><th>Required</th></tr></thead><tbody><tr><td><p>Max In Memory Size</p></td><td><div><div><p>Number</p></div></div></td><td><p>This is the maximum amount of instances that will be kept in memory. If more than that is required, then it will start to buffer the content on disk.</p></td><td></td><td></td></tr><tr><td><p>Buffer Unit</p></td><td><div><div><p>Enumeration, one of:</p></div><div><ul><li><p>BYTE</p></li><li><p>KB</p></li><li><p>MB</p></li><li><p>GB</p></li></ul></div></div></td><td><p>The unit in which maxInMemorySize is expressed</p></td><td></td><td></td></tr></tbody></table>

## See Also

[Salesforce Help](https://help.salesforce.com)

<!-- document id=9acae592b86cac8a12b17d0b3c683c1f16d7d37cb97e05e0df503b1dc631cd94 url=/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/ms-dynamics-nav-connector-upgrade-migrate.md -->

---
product: Microsoft Dynamics NAV Connector
version: 3.0
---

# Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 3.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Upgrade Anypoint Connector for Microsoft Dynamics NAV Connector to version 3.x.

## Supported Upgrade Paths

<table><colgroup><col> <col></colgroup><thead><tr><th>From Version</th><th>To Version</th></tr></thead><tbody><tr><td><div><div><p>2.x</p></div></div></td><td><div><div><p>3.x</p></div></div></td></tr></tbody></table>

## Changes in This Release

To support Microsoft Dynamics NAV Connector in CloudHub 2.0, the client must provide SOAP requests
in raw XML format instead of using Plain Old Java Objects (POJOs).

Follow these steps to send or receive SOAP requests in raw XML format:

1.  Make sure you have the prerequisites, such as Mule 4.6.6 or later, and obtain the WSDL file.

2.  Identify all Mule flows that use Microsoft Dynamics NAV SOAP operations.

3.  For the request body, update the content type to `application/xml` and provide SOAP requests in
    raw XML format instead of using POJOs.

    ![Page Operation Configuration](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/_images/ms-dynamics-nav-page-config.png)

    XML for sending SOAP requests directly:

    ```xml
    <item:Read xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:item="urn:microsoft-dynamics-schemas/page/item_card">
          <item:No>1000</item:No>
       </item:Read>
    ```

    ![Transform message of Page Operation](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/3.0/_images/ms-dynamics-nav-page-output.png)

    XML for using the DataWeave transform method to convert JSON to XML payload:

    ```xml
    <ee:transform doc:name="Transform Message" doc:id="52c376d8-70de-44b3-b388-4837f0790795">
           <ee:message>
               <ee:set-payload><![CDATA[%dw 2.0
       output application/xml
       ---
       {
           Read @("xmlns": "urn:microsoft-dynamics-schemas/page/item_card"): {
               No: 1000
           }
       }]]></ee:set-payload>
           </ee:message>
       </ee:transform>
    ```

4.  For the response body, you will receive SOAP responses in raw XML format and must handle these
    responses accordingly.

    XML of a SOAP response:

    ```xml
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:item="urn:microsoft-dynamics-schemas/page/item_card">
       <soapenv:Header/>
       <soapenv:Body>
          <item:Read_Result>
             <item:Item>
                <item:No>Returned_1000</item:No>
                <item:Description>Returned_Awesome_Product</item:Description>
                <item:UnitPrice>100.00</item:UnitPrice>
             </item:Item>
          </item:Read_Result>
       </soapenv:Body>
    </soapenv:Envelope>
    ```

    XML for using the DataWeave method to transform XML payload:

    ```xml
    <ee:transform doc:name="Transform Response">
        <ee:message>
            <ee:set-payload><![CDATA[%dw 2.0
    output application/java
    ns soapenv http://schemas.xmlsoap.org/soap/envelope/
    ns item urn:microsoft-dynamics-schemas/page/item_card
    ---
    payload.soapenv#Envelope.soapenv#Body.item#Read_Result.item#Item
    ]]></ee:set-payload>
        </ee:message>
    </ee:transform>
    ```

## Upgrade Prerequisites

Before you perform the upgrade, you must create a backup of your files, data, and configurations in
case you need to restore to them.

## Upgrade Steps

Follow these steps to perform the upgrade:

1.  In Anypoint Studio, create a Mule project.

2.  In the **Mule Palette** view, click **Search in Exchange**.

3.  In **Add Dependencies to Project**, enter `dynamics nav` in the search field.

4.  In **Available modules**, select **Microsoft Dynamics NAV** and click **Add**.

5.  Click **Finish**.

6.  Verify that the Microsoft Dynamics NAV Connector dependency version is `3.0.0` in the `pom.xml`
    file in the Mule project.

Studio upgrades the connector automatically.

### Verify the Upgrade

After you install the latest version of the connector, follow these steps to verify the upgrade:

1.  In Studio, verify that there are no errors in the **Problems** or **Console** views.

2.  Verify that there are no problems in the project `pom.xml` file.

3.  Test the connection to verify that the operations work.

## Troubleshoot

If there are problems with caching the parameters and caching the metadata, try restarting Anypoint
Studio.

### Revert the Upgrade

If it is necessary to revert to the previous version of Microsoft Dynamics NAV Connector, change the
`ms-dynamics-nav-connector` dependency version `3.0.0` in the project’s `pom.xml` to the previous
version.

You must update the project’s `pom.xml` in Anypoint Studio.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Microsoft Dynamics NAV Connector Reference](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/3.0/ms-dynamics-nav-connector-reference)

- [Salesforce Help](https://help.salesforce.com)

<!-- document id=1ea898dc78e598093c1c2e9e014cc098894932b903a63b7ff1e080bc6e61b2e3 url=/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-upgrade-migrate.md -->

---
product: Microsoft Dynamics NAV Connector
version: 4.0
is-latest-version: true
---

# Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 4.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Upgrade Anypoint Connector for Microsoft Dynamics NAV (Microsoft Dynamics NAV Connector) from
version 3.x to version 4.x.

## Supported Upgrade Paths

<table><colgroup><col> <col></colgroup><thead><tr><th>From Version</th><th>To Version</th></tr></thead><tbody><tr><td><div><div><p>3.x</p></div></div></td><td><div><div><p>4.x</p></div></div></td></tr></tbody></table>

## Changes in This Release

### 4.0

- This connector is now compatible with Java 17 only.

- The SOAP stack now uses Apache CXF 4.2.4 and the Jakarta XML Bind, XML Web Services, JWS, and SOAP
  APIs. Applications that depend on Apache CXF 3 or the Java EE JAXB, JAX-WS, JWS, or SAAJ packages
  must be re-verified. Operation names and the `nav` configuration prefix are unchanged.

- The NTLM and OAuth connection types now include optional **Response Timeout** and **Response
  Timeout Unit** fields on the Advanced tab. The default response timeout is 5000 milliseconds.
  Expressions aren’t supported for these fields.

  For more information, see [NTLM Connection Type](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#ntlm) and
  [OAuth Connection Type](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference#dynamics-nav-config_oauth).

- The JAXB-XJC external library for the NTLM and OAuth connection types is now
  `org.glassfish.jaxb:jaxb-xjc:4.0.9`. Version 3.x used `com.sun.xml.bind:jaxb-xjc:2.3.9`.

- These libraries are upgraded to address reported security vulnerabilities:

  - The Apache CXF library is upgraded to version 4.2.4.

  - The JAXB runtime and XJC libraries are upgraded to version 4.0.9.

  - The Jakarta XML Bind API is upgraded to version 4.0.5.

  - The Apache Commons Lang library is upgraded to version 3.21.0.

- These libraries are added to address reported security vulnerabilities:

  - The Jakarta XML Web Services API is added at version 4.0.3.

  - The Jakarta XML SOAP API is added at version 3.0.2.

  - The Jakarta JWS API is added at version 3.0.0.

  - The SAAJ implementation is added at version 3.0.6.

  - The Bouncy Castle libraries are added at version 1.86.

## Requirements

Ensure your system meets the following compatibility requirements before you perform the upgrade:

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule runtime</p></td><td><p>4.9.0 and later</p></td></tr><tr><td><p>Java</p></td><td><p>17</p></td></tr><tr><td><p>Microsoft Dynamics NAV</p></td><td><div><div><ul><li><p>2013 R2</p></li><li><p>2015</p></li><li><p>2016</p></li><li><p>2017</p></li></ul></div></div></td></tr></tbody></table>

## Upgrade Prerequisites

Before you perform the upgrade, you must:

1.  Create a backup of your files, data, and configuration in case you need to restore to the
    previous version.

2.  Ensure that your environment meets the version 4.x requirements, including Java 17 and Mule
    runtime 4.9.0 or later.

3.  Re-verify applications that depend on Apache CXF 3 or the Java EE JAXB, JAX-WS, JWS, or SAAJ
    packages.

4.  Update the JAXB-XJC external library to `org.glassfish.jaxb:jaxb-xjc:4.0.9` for the NTLM and
    OAuth connection types.

5.  Install Microsoft Dynamics NAV Connector 4.x to replace the connector operations that were
    previously included in version 3.x.

## Upgrade Steps

Follow these steps to perform the upgrade from Microsoft Dynamics NAV Connector 3.x to Microsoft
Dynamics NAV Connector 4.x:

1.  In Anypoint Studio, create a Mule project.

2.  In the Mule Palette view, click **Search in Exchange**.

3.  In the **Add Dependencies to Project** window, enter `dynamics nav` in the search field.

4.  In the **Available modules** section, select **Microsoft Dynamics NAV** and click **Add**.

5.  Click **Finish**.

6.  Verify that the `mule-microsoft-dynamics-nav-connector` dependency version is `4.x.x` in the
    `pom.xml` file, where `x.x` is the minor release and patch version number. For example, if you
    are upgrading to version 4.0, the dependency version in the `pom.xml` file should be `4.0.0`.

Studio upgrades the connector automatically.

## Verify the Upgrade

After you install the latest version of the connector, follow these steps to verify the upgrade:

1.  In Studio, verify that there are no errors in the **Problems** or **Console** views.

2.  Check the project `pom.xml` file and verify that there are no problems.

3.  Test the connection and verify that the operations work.

## Troubleshooting

If there are problems with caching the parameters and caching the metadata, try restarting Studio.

## Revert the Upgrade

If it is necessary to revert to the previous version of Microsoft Dynamics NAV Connector, change the
`mule-microsoft-dynamics-nav-connector` dependency version in the project’s `pom.xml` file to the
previous version.

You must update the project’s `pom.xml` file in Anypoint Studio.

## Send SOAP Requests in XML Format

To support Microsoft Dynamics NAV Connector in CloudHub 2.0, the client must provide SOAP requests
in raw XML format instead of using Plain Old Java Objects (POJOs).

Follow these steps to send or receive SOAP requests in raw XML format:

1.  Make sure you have the prerequisites, such as Mule 4.9.0 or later, and obtain the WSDL file.

2.  Identify all Mule flows that use Microsoft Dynamics NAV SOAP operations.

3.  For the request body, update the content type to `application/xml` and provide SOAP requests in
    raw XML format instead of using POJOs.

    ![Page Operation Configuration](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/_images/ms-dynamics-nav-page-config.png)

    XML for sending SOAP requests directly:

    ```xml
    <item:Read xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:item="urn:microsoft-dynamics-schemas/page/item_card">
          <item:No>1000</item:No>
       </item:Read>
    ```

    ![Transform message of Page Operation](/mulesoft/current/en-us/microsoft-dynamics-nav-connector/latest/_images/ms-dynamics-nav-page-output.png)

    XML for using the DataWeave transform method to convert JSON to XML payload:

    ```xml
    <ee:transform doc:name="Transform Message" doc:id="52c376d8-70de-44b3-b388-4837f0790795">
           <ee:message>
               <ee:set-payload><![CDATA[%dw 2.0
       output application/xml
       ---
       {
           Read @("xmlns": "urn:microsoft-dynamics-schemas/page/item_card"): {
               No: 1000
           }
       }]]></ee:set-payload>
           </ee:message>
       </ee:transform>
    ```

4.  For the response body, you will receive SOAP responses in raw XML format and must handle these
    responses accordingly.

    XML of a SOAP response:

    ```xml
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:item="urn:microsoft-dynamics-schemas/page/item_card">
       <soapenv:Header/>
       <soapenv:Body>
          <item:Read_Result>
             <item:Item>
                <item:No>Returned_1000</item:No>
                <item:Description>Returned_Awesome_Product</item:Description>
                <item:UnitPrice>100.00</item:UnitPrice>
             </item:Item>
          </item:Read_Result>
       </soapenv:Body>
    </soapenv:Envelope>
    ```

    XML for using the DataWeave method to transform XML payload:

    ```xml
    <ee:transform doc:name="Transform Response">
        <ee:message>
            <ee:set-payload><![CDATA[%dw 2.0
    output application/java
    ns soapenv http://schemas.xmlsoap.org/soap/envelope/
    ns item urn:microsoft-dynamics-schemas/page/item_card
    ---
    payload.soapenv#Envelope.soapenv#Body.item#Read_Result.item#Item
    ]]></ee:set-payload>
        </ee:message>
    </ee:transform>
    ```

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Microsoft Dynamics NAV Connector Reference](https://docs.mulesoft.com/microsoft-dynamics-nav-connector/latest/ms-dynamics-nav-connector-reference)

- [Salesforce Help](https://help.salesforce.com)