Upgrading and Migrating Microsoft Dynamics NAV Connector to Version 4.0

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

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

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

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

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

In Anypoint Studio, create a Mule project.

In the Mule Palette view, click Search in Exchange.

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

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

Click Finish.

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.

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

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

Test the connection and verify that the operations work.

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

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

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

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

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

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

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

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