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 Finance and Operations platform update 24. This version has a build number of 7.0.5179. For more information about Platform update 24, see Additional resources.
New APIs
New APIs help data integration retrieve errors that occurred during the import execution runs in a data project. Those APIs are:
- GetImportTargetErrorKeysFileUrl
- GenerateImportTargetErrorKeysFile
- GetImportStagingErrorFileUrl
For more information, see Data management package REST API.
Clear identification of preview builds
Some partners, ISVs, and customers access preproduction builds of Finance and Operations by being part of the Preview Early Access Program (PEAP) or by using public previews of the service. This preview phase is intended as a mechanism for feedback on the latest features and for validation of customizations. These early releases, however, aren't authorized for production use. See the Service update availability article for more information about the Finance and Operations release process.
To make the preview status clear to users, each preproduction build is tagged in two different ways:
Users see the word "Preview" as a suffix to the product name in the navigation bar.
The title of the About box includes the word "Preview".
Updated navigation bar that aligns with the Office header
Dynamics 365 products are aligning their respective headers with the Office header to provide a more cohesive shell experience for users across Microsoft products. For Finance and Operations users, this header update appears as a completely restyled navigation bar that more prominently features navigation search. Notably, the new design doesn't include a breadcrumb.
The updated navigation bar appears by default in Platform update 24. If you want to continue using the older navigation bar, you can temporarily switch to it via the Client performance options page, specifically by using the Enable legacy navigation bar toggle. We plan to make this toggle available through Platform update 28 only, at which time all customers will see the updated navigation bar.
The following image shows the updated navigation bar in Platform update 24.
The following image shows how the navigation bar appeared in Platform update 23.
Extensibility enhancements
The first wave of platform extensibility enhancements, included in Platform update 24, are documented in the April 2019 Release notes. The documentation details nine enhancements, with one of the highlights being a new onClicking event for form button controls.
Client Alert support for email notifications
Stay on top of your business data with integrated change tracking tools. With Platform update 24, you can create Alert Rules that automatically dispatch email notifications to contacts when triggered by an event. This capability is the most requested feature in the Dynamics Ideas customer forum. With Dynamics 365 for Finance and Operations, you can define custom Alert rules to monitor filtered views of your data. The option of receiving email notifications is available for all supported Alert types and can be enabled for existing Alert rules.
Supported scenarios include using intuitive controls to create Alerts rules that monitor filtered views of System batch jobs. Move beyond the burden of constantly checking reports for changes to business data and let the Dynamics 365 for Finance and Operations intelligent change detection service do the monitoring for you.
Business events (Private preview)
This new capability provides a framework that allows business processes in Finance and Operations to capture business events as business processes execute, and send the events to an external system or application.
Note
This feature is available as a private preview. For information about when the feature is scheduled for general availability, see the Release plans.
For example, a purchase order approval can quickly trigger a fulfillment in the vendor organization; a receipt of a damaged part can trigger the vendor claim process in real time; and so on. Because these events happen in the context of business processes, they're called business events, which enable business process integration.
External business processes can subscribe to specific business events from Finance and Operations to get notified when they occur. You can also use the business events as "triggers" in the Finance and Operations connector.
Some capabilities that are included are:
Business events framework, for partner and customer implemented business events.
Business events administrator experience.
Application business events.
Workflow business events.
Out-of-the-box integration with Azure Event Grid and Azure Service Bus for advanced integration scenarios.
Exposing business events as 'triggers' in Microsoft Power Automate.
For more information, see Business events overview.
Additional resources
Platform update 24 bug fixes
For information about the bug fixes included in each of the updates that are part of Platform update 24, sign in to Lifecycle Services and view this KB article.
Dynamics 365 April '19 release notes
Wondering about upcoming and recently released capabilities in any of our business apps or platform?
Check out the April '19 release notes. We've captured all the details, end to end, top to bottom, in a single document that you can use for planning.
Removed and deprecated features
The Removed or deprecated features for Finance and Operations article describes features that we removed or deprecated for Dynamics 365 for Finance and Operations.
- A removed feature is no longer available in the product.
- A deprecated feature isn't in active development and might be removed in a future update.
Before we remove any feature from the product, we announce the deprecation notice in the Removed or deprecated features for Finance and Operations article 12 months prior to the removal.
For breaking changes that only affect compilation time but are binary compatible with sandbox and production environments, the deprecation time is less than 12 months. Typically, these changes are functional updates that you need to make to the compiler.