Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.
This article describes features that are new or changed in Dynamics 365 for Operations platform update 5. This version was released in March 2017 and has a build number of 7.0.4475.16165.
Development and customization
| Feature | Why this is important |
|---|---|
| EventHandlerResult classes in request or response scenarios | You can now use the EventHandlerResult class for scenarios where the delegate (event) logic requires its subscribers (event handlers) to provide at least one response so that no result is lost when there are multiple subscribers and multiple results. |
| Customization Analysis Report (CAR) justification | When you suppress a best practice warning within a suppression file in the AxIgnoreDiagnosticList folder of your model, and include a justification, the justification text appears in the CAR report of your model. For an example of a suppression file that includes justifications, see <Packages Local Directory>\Directory\Directory\AxIgnoreDiagnosticList\Directory_BPSuppressions.xml. |
| Telemetry | When you build a model, the telemetry framework collects information about Microsoft classes and methods that customer and ISV code reference. This process provides Microsoft with much needed information regarding what part of the standard application code is included in backward compatibility requirements. |
| X++ compiler and try catch blocks | The X++ compiler now generates code that is slightly different for try catch blocks. Before, the system caught the DuplicateKey and UpdateConflict exceptions as part of the catch all clause. This approach introduced some problems that could ultimately lead to data consistency problems if the try catch was used when a transaction is running. Now, the two exceptions mentioned, which are special because they don't roll back a running transaction, are no longer caught in the catch all. For more information, see the blog post X++, the catch. |
Personalization
| Feature | Why this is important |
|---|---|
| Enhanced administration features for personalization | The personalization administrator can now apply or remove form personalizations for groups of users. Previously, you could only perform personalization administration one user at a time. For more information, see Personalize the user experience. |