Contact Us 1-800-596-4880
  1. Homepage
  2. Microsoft Dynamics GP Connector (3.0)

  3. Upgrading and Migrating Microsoft Dynamics GP Connector

All Connectors

Upgrading and Migrating Microsoft Dynamics GP Connector to 3.x

Upgrade Anypoint Connector for Microsoft Dynamics GP (Microsoft Dynamics GP Connector) from version 2.x to version 3.x.

Supported Upgrade Paths

From Version To Version

2.x

3.x

Changes in This Release

3.0

  • This connector is now compatible with Java 17 only.

  • Connector failures are now reported as DYNAMICSGP:DYNAMICSGP_INTERNAL, instead of DYNAMICSGP:UNKNOWN. A condition on ANY still matches DYNAMICSGP:DYNAMICSGP_INTERNAL and DYNAMICSGP:XML_PARSING. A handler that names DYNAMICSGP:UNKNOWN doesn’t match this release.

  • You can now set optional Timeout unit, Connection timeout, and Read timeout fields on the Default Configuration Advanced tab. Each operation can override these values in the Timeout Override group on the Advanced tab. An override applies when you set Connection Timeout or Read Timeout. When you don’t set those values, the Kerberos Authentication Timeout Configuration values remain in effect.

  • Generated sources and WSDL bindings now use Jakarta XML packages, instead of Java EE packages. Operation names, the XML namespace, and the dynamicsgp configuration prefix are unchanged.

  • These libraries are upgraded to address reported security vulnerabilities:

    • The Apache CXF library is upgraded to version 4.2.4.

    • The Web Services Security library is upgraded to version 4.0.2.

    • The Apache XML Security (Santuario) library is upgraded to version 4.0.4.

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

    • The Apache Neethi library is upgraded to version 3.2.4.

    • The Apache Xerces library is upgraded to version 2.12.2.

  • These libraries are added to address reported security vulnerabilities:

    • The Guava library is added at 33.7.2-jre.

    • The Apache XMLSchema Core library is added at 2.3.3.

    • The Jakarta XML Binding API library is added at 4.0.5.

    • The Jakarta XML Web Services library is added at 4.0.3.

    • The Jakarta XML SOAP Binding library is added at 3.0.2.

    • The Jakarta annotation API library is added at 2.1.1.

    • The JAXB runtime library is added at 4.0.9.

    • The SAAJ implementation library is added at 3.0.6.

    • The ASM library is added at 9.11. This pin replaces ASM 9.10.1 from Apache CXF 4.2.4 and addresses CVE-2026-110257, CVE-2026-110258, CVE-2026-110259, CVE-2026-110260, CVE-2026-110261, and CVE-2026-110263.

Requirements

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

Application/Service Version

Mule runtime

4.9.0 and later

Java

17

Microsoft Dynamics GP

  • 2010 R2

  • 2013 (Version 12)

  • 2013 R2

  • 2015 (Version 14)

  • 2015 R2

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 3.x requirements, including Java 17 and Mule runtime 4.9.0 or later.

  3. If an error handler names DYNAMICSGP:UNKNOWN, update it to DYNAMICSGP:DYNAMICSGP_INTERNAL. A condition on ANY still matches DYNAMICSGP:DYNAMICSGP_INTERNAL and DYNAMICSGP:XML_PARSING.

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

Upgrade Steps

Follow these steps to perform the upgrade from Microsoft Dynamics GP Connector 2.x to Microsoft Dynamics GP Connector 3.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 Microsoft Dynamics GP in the search field.

  4. In the Available modules section, select Microsoft Dynamics GP Connector and click Add.

  5. Click Finish.

  6. Verify that the mule-microsoft-dynamics-gp-connector dependency version is 3.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 3.0, the dependency version in the pom.xml file should be 3.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.

  4. If the application handles DYNAMICSGP:UNKNOWN, confirm that the handler now uses DYNAMICSGP:DYNAMICSGP_INTERNAL.

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 GP Connector, change the mule-microsoft-dynamics-gp-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.

See Also

Back to top