Microsoft Dynamics 365 for Finance and Operations/AX Release Notes
Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.
See TIBCO Scribe® Online Connector for Microsoft Dynamics 365 for Finance and Operations/AX for more information.
Version 1.2.0
Released March 16, 2023.
New And Noteworthy
- TIBCO has tested the TIBCO Cloud™ Integration - Connect Connector For Microsoft Dynamics 365 for Finance and Operations/AX against Microsoft Dynamics 365 for Finance and Operations/AX 8.0. TIBCO has validated that Microsoft Dynamics 365 for Finance and Operations/AX features supported by the Connector for prior versions of Microsoft Dynamics 365 for Finance and Operations/AX continue to be supported for Microsoft Dynamics 365 for Finance and Operations/AX 8.0. (35838)
- Added support for OData V7.10 libraries. (SCMSAX-10)
- Added support for Client Secret authentication. (SCMSAX-59)
- Added support for throttling requests. When a throttle limit or request limit exceeded error is received, the Microsoft Dynamics 365 for Finance and Operations/AX Connector retries once using the delay returned by Microsoft Dynamics 365 for Finance and Operations/AX. This delay throttles or slows down the entire flow. (SCMSAX-18)
- Added Send operation functionality which is used to make API Calls to the Microsoft Dynamics 365 for Finance and Operations/AX API. The Send operation supports the Request entity used to build the HTTP calls to the API. (SCMSAX-72)
Changes in Functionality
Closed Issues
SCMSAX-15
The Microsoft Dynamics 365 for Finance and Operations/AX now contains a warning indicating that the "Is Not Like" and "Is Like" Query filter operators are not supported. For the "is like"operator, use the "equals" operator and use an "*" as a wild card character. The "is not like" operator does not have a similar alternative.
49905 / 58995
Lookup and Update Patch operations did not recover from Timeout Exceptions, which caused a performance degradation. (Case # 59311, 60713, 62869, 63357, 64065, 60477, 63560, 63681, 66972, 01721048, 01723097, 01723573, 01723745, 01723864, 01727098, 01724221, 01770670, 01824129)
SCMSAX-83 / 59084 / 62845
Debugging a Request / Reply flow generated an error similar to the following: (Case # 63052, 62606, 67362, 68326, 01723276, 01722874, 01727487, 01728447)
Entity error: Type 'Microsoft.OData.Core.ODataEnumValue' cannot be serialized.
SCMSAX-96
Authentication tokens were not always being refreshed correctly causing errors similar to the following: (Case # 02042664. 02042968)
Operation failed. Label: Lookup Person Party Number, Name: PersonUsersLookup, Message: A supported MIME type could not be found that matches the content type of the response. None of the supported type(s)"
Known Issues
SCMSAX-284
Summary: Due to a limitation in OData metadata, the Microsoft Dynamics 365 for Finance and Operations/AX Connector appears to support create, insert, update, or delete operations for some entities and fields that do not support these operations. In such cases, errors similar to the following are generated:
Insert not allowed.
Insert not allowed for field <field name>.
Workaround: None.
45634
Summary: Mapping a value to the Terms of Payment field in Microsoft Dynamics 365 for Finance and Operations/AX using Update Patch deletes or leaves the field value blank. (Case # 59375)
Workaround: None.
40463
Summary: When using a compound primary key as Matching Criteria, the Delete operation does not find or delete any RetailInfoCodeAssociations entity records. (Case # 55373)
Workaround: None.
Version 1.1.0
TIBCO Scribe® released the Version 1.1 update to the Connector for Microsoft Dynamics 365 for Finance and Operations/AX on July 31, 2017.
New And Noteworthy
Rebranded the Connector to Scribe Connector For Microsoft Dynamics 365 For Operations / AX7 to match Microsoft product name updates. (43289)
Closed Issues
47808
When processing a large number of records in an environment with several Connect on-premise agents running simultaneously, sometimes 401 unauthorized exceptions were generated. (Case # 89441).
47810
Using multiple Connect on-premise agents running concurrent apps sometimes caused credentials for connecting to Microsoft Dynamics 365 for Finance and Operations/AX via TIBCO Cloud™ Integration - Connect to be corrupted and generated the following message: Accessing WS metadata exchange failed. (Case # 55832, 56787)
47811
If the datetime field submitted during an Update Patch on the CustomerPostalAddress entity was not in the Z datetime format errors were generated and the Update Patch failed. Now, the datetime value is converted to the correct format before it is sent to Microsoft Dynamics 365 for Finance and Operations/AX. (Case # 58044)