Microsoft Dynamics 365 Connector Release Notes - Mule 3

Fixed all operations that caused the connector to throw a "Timeout waiting for connection from pool" exception. (SE-16614 and SE-16738)

When using the Create operation, the connector was threw a "Timeout waiting for connection from pool" exception. (SE-15050)

Added support for nested related objects (known as deep insert). (SE-11360)

Added logging to the DEBUG level to help with troubleshooting.

Fixed a bug with space encoding. (SE-12460)

This connector now supports API version 9.x and later, by making the version number configurable.

Enhanced exception handling in case of bad credentials.

The plus sign (+) was not correctly encoded when executing a query, which caused the operation to not return the results.

Mule 3.6 is no longer supported.

No new features added.

Dynamics 365 Connector stopped making calls after the maximum number of connections (maxHttpConnections). Even if no value was set, it stopped when 100 (default value) was reached. The issue was fixed by removing the HTTP request from the request pool.

Under certain scenarios, connections were being kept open after performing requests. This was fixed.

No new features added

An issue was reported that when using a payload with Czech characters in the connector, an error is returned even if the Mule message is set to use UTF-8 encoding. It was fixed by using the correct UTF-8 encoding in the requests to the Dynamics 365 service.

No new features added.

Fixed Read Timeout default value. Default was always 5 seconds even if setting was not specified or set to 0. Now, if ReadTimeout is not specified, the default is 5 seconds, else if ReadTimeout is less or equal to 0 (zero), the default is an infinite wait.

No new features added.

Dynamics 365 Connector was not releasing immediately the connections with an error response (HTTP error code >= 400). The Olingo protocol doesn’t release a connection immediately if the response is not consumed, so we forced the connector to consume the response even if it’s an error response.

No new features added.

This connector was throwing a TimeOutException after receiving a 204 response from the API for an update operation. This was happening because the HTTP client we are using has some memory leaks and we had to override the default implementation.

This connector was throwing a TimeOutException after 30 seconds even if the configured timeout value was greater. Now the exception is thrown after the configured timeout value.

This connector was creating a new connection for each request, not using the maximum number of connections configured in the pool. Another issue here was that the connections were never released. Now the issues are fixed.

This connector does not refresh OAuth token after expiration.

Creating an entity with a GUID using this connector throws metadata error.

This connector does not support Edm.Date.

Fixed the edm.datetimeoffset issue.

Null values not accepted for Int32 fields.

Error when converting decimal fields.

Unauthorized (HTTP/1.1 401 Unauthorized) error raised when token expired.