What's new or changed in Platform update 29 for finance and operations apps (October 2019)
This article describes features that are new or changed in Platform update 29 for finance and operations apps. This version has a build number of 7.0.5372. While the general availability date is in October, the new features are available for early release in August. For more information about Platform update 29, see Additional resources.
The Feature management experience provides a workspace where you can view a list of features that have been delivered in each release. In Platform update 29, additional features have been added, including:
- Enable all features that aren't enabled.
- Automatically enable all features after an update.
- Don't allow a feature to be enabled based on a condition, such as an existing config key is turned on.
- Add a button called Check for updates that manually searches for new features and adds them to the list of features.
For more information, see Feature management overview.
Data management job history clean up
Job history cleanup functionality in Data management must be used to schedule a periodic cleanup of the execution history. This functionality replaces the existing staging table cleanup functionality, which is now deprecated.
Business events catalog security
Role-based security can be now applied to individual business events in the business event catalog. When this security is enabled and configured, users will be able to only view and subscribe to business events to which their roles have access. This security also applies to integration scenarios, such as Microsoft Flow.
An attachment recovery feature has been added that provides a recycle bin for record attachments. For a configured period of time after deletion, users and administrators can recover deleted attachments using the new deleted attachments forms. For details, see Configure document management.
Session idle timeout
The session idle timeout is the amount of time a user can be inactive before the user's session times out and is closed. With Platform update 29, the web browser session timeout setting is exposed in the user interface and is optimized for a default value of 30 minutes instead of 60 minutes. You can still change and set the value up to 60 minutes, but that may cause an extra load on the system. For more information, see Set the session idle timeout.
Visual refresh of the web client to align with the Fluent design language
As part of the Dynamics 365 app-wide effort, we're incrementally working toward a visual refresh of the web client to more closely align controls and pages with the Microsoft Fluent design language. An initial set of changes are included in Platform update 29. For more information, see the Visual refresh of the web client to align with the Fluent design language article in the Release Plans.
As part of this change, the workspace tiles on the dashboard now have a new visual style. See Create icons for workspace tiles for updated guidance on creating images for workspace tiles that are visually aligned to out-of-the-box workspace tiles.
Saved views (Preview)
Saved views are now available in preview. This feature represents a significant enhancement to the personalization subsystem, and allows users to have multiple named sets of personalizations per page. For list pages, these views can also contain filters. Management of personalizations is also substantially easier with views, as views can be published to security roles. For more information about how to enable this feature in a developer environment, see Saved views. Also refer to the Build forms that fully utilize saved views article. Note that this preview feature will continue to evolve and change until it becomes generally available.
New grid control (Preview)
The new grid control is now available in preview. This new grid serves as a replacement for the existing grid control and features faster rendering, smoother scrolling, easier navigation in the grid, and drag-and-drop column reordering. The new grid also allows for grand totals at the bottom of numeric columns in tabular grids in a footer that can be enabled using the right-click context menu from column headers. Once enabled, all tabular and list grids will automatically switch to use the new grid, unless the page has a grid with a nonreact extensible control, in which case the existing grid control will be used on that page. Note that this preview feature will continue to evolve and change until it becomes generally available.
To try out the new grid control, add &debug=reactGrid into the URL of your developer environment. Note that flighting will prevent the feature from being operational in other environments.
Workflow work item notifications in the action center
Users can now opt-in to receive notifications in the Action Center by going to Settings > User options > Workflow > Notifications > Send notifications to Action Center. When enabled, the user will receive a notification for each new work item that is assigned to them.
Workflows can now support reset
Workflows can now support reset from the Workflow History form by optionally implementing the WorkflowIRecallUnrecoverable interface. The vendor invoice workflow has used this interface to allow unrecoverable vendor invoice workflows to be recalled and placed in a canceled state.
Workflow deletion will confirm business event subscription deletions
When business event subscriptions associated with the workflow are found, a confirmation dialog box provides a list of any related business event subscriptions so that the user is fully aware of the effects of deleting the workflow.
Improved payloads for workflow business events
Standard workflow context has been added to the payloads for all Workflow Business Events including owner, originator, and last note.
Flow templates for workflow work item
Flow templates have been created to provide a useful starting point for building flows that facilitate work item completion. For more information, see Workflow business events.
The following enhanced extensibility capabilities have been added in Platform update 29:
- Enable extension of WorkflowApproval properties, WorkflowTask properties, and addition of WorkflowOutcomes into a WorkflowTask (Ref# 198831).
- Enable event triggering for fields on forms that come from table field groups (Ref# 247364).
- Enable the use of the FormObservable attribute in class declarations (Ref# 198797).
- Add model name to extension default naming to reduce conflicts (Ref# 300468).
- Enable use of extension table fields in form datasources and security privileges (Ref# 315634).
- Custom privilege for a standard form control should consider needed permission property value set on extension form (Ref# 313650).
- Allow table display methods added via extension to be used as lookup methods (Ref# 243486).
- Enable display methods to be added to Form Datasources via extension (Ref# 256004).
CodeLens for method references in the X++ editor
The X++ source code editor now takes advantage of the CodeLens functionality of Visual Studio. The number of references to an X++ method is shown in CodeLens right above the method declaration line. You can click on the reference count to find all references to the method.
Platform update 29 bug fixes
For information about the bug fixes included in each of the updates that are part of Platform update 29, sign in to Lifecycle Services (LCS) and view this KB article.
Dynamics 365: 2019 release wave 2 plan
Wondering about upcoming and recently released capabilities in any of our business apps or platform?
Check out the Dynamics 365: 2019 release wave 2 plan. 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 have been removed or deprecated.
- A removed feature is no longer available in the product.
- A deprecated feature isn't in active development and may be removed in a future update.
Before any feature is removed from the product, the deprecation notice is announced 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 need to be made to the compiler.