Microsoft Dynamics NAV Connector Release Notes
Support Category: Select
Anypoint Connector for Microsoft Dynamics NAV Connector (NAV Connector) enables Mule apps to interact with the Microsoft Dynamics NAV Web Services versions 2013 R2, 2015, 2016, 2017.
4.0.0
October 23, 2026
What’s New
-
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
navconfiguration 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 and OAuth Connection Type.
-
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 usedcom.sun.xml.bind:jaxb-xjc:2.3.9.For more information, see NTLM Connection Type and OAuth Connection Type.
For more information about how to upgrade, see Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 4.0.
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.9.0 and later |
OpenJDK |
17 |
Microsoft Dynamics NAV |
|
Fixed Issues
| Issue Resolution | ID |
|---|---|
These libraries are upgraded to address reported security vulnerabilities:
These libraries are added to address reported security vulnerabilities:
|
W-24113950, W-3300013 |
3.0.2
September 21, 2026
What’s New
-
This release includes general security fixes.
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.6.6 and later |
OpenJDK |
8, 11, and 17 |
Fixed Issues
| Issue Resolution | ID |
|---|---|
These libraries are upgraded to address reported security vulnerabilities:
|
W-3300013 |
3.0.1
August 21, 2026
What’s New
-
This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime, use the connector version released immediately after this one.
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.6.6 and later |
OpenJDK |
8, 11, and 17 |
Fixed Issues
| Issue Resolution | ID |
|---|---|
These libraries are upgraded to address reported security vulnerabilities:
|
W-23441858 |
3.0.0
July 4, 2025
What’s New
-
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.
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.6.6 and later |
OpenJDK |
8, 11, and 17 |
2.1.0
August 20, 2024
What’s New
-
This connector is now compatible with Java 17.
-
A new external library called JAXB-XJC is now required for the NTLM and OAuth connection types for Java 8, 11, and 17. For more information, refer to NTLM Connection Type and OAuth Connection Type.
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.1.1 and later |
OpenJDK |
8, 11, and 17 |
2.0.12
October 3, 2022
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.1.1 and later |
Fixed Issues
| Issue | ID |
|---|---|
The metadata for the Page Operation operation now works as intended. |
W-11791738 |
2.0.11
November 11, 2021
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.1.1 and later |
Fixed Issues
| Issue | ID |
|---|---|
Fixed reported security vulnerabilities. |
CONN-9261 |
2.0.10
September 20, 2021
Compatibility
| Application/Service | Version |
|---|---|
Mule |
4.0.0 and later |
Fixed Issues
| Issue | ID |
|---|---|
Optimized the connector to improve its overall stability and performance. |
CONN-8802 |
2.0.1
June 10, 2019
Fixed Issues
-
NAV Connector Test Connection fails with Unable to create JAXBContext for generated packages - There were some issues with some dependencies of the connector that were causing this problem with Mule runtime 4.2.0 and later. This was fixed by upgrading some dependencies to newer versions: org.apache.cxf:cxf-rt-transports-http:3.2.1 was updated to org.apache.cxf:cxf-rt-transports-http:3.3.1 and org.apache.cxf:cxf-rt-frontend-jaxws:3.2.1 was updated to org.apache.cxf:cxf-rt-frontend-jaxws:3.3.1. (SE-11902)