Released version 9.1 19051

  • Article

Introduction

Version 9.1 19051 for Microsoft Dataverse is now available in all regions. This article describes the updates, including the new features, and the fixes to existing functionality, which are included in this update. This version was first made available in preview on May 15, 2019, and completed worldwide rollout on June 8, 2019.

Automated flow parity with classic Common Data Service workflows improvements

Automated flows will, over time, replace the existing Classic Common Data Service workflows (formerly known as Dynamics 365 for Customer Engagement workflow). With this release, it is now possible to accomplish the majority of scenarios that asynchronous classic Common Data Service workflows supported with automated flows. Several capabilities, including action support support, are covered elsewhere in the release notes.

  • Filter triggers based on which attributes change - You can control which field changes trigger your automated flows. For example, trigger your flow only when the status field changes - but ignore all other fields that may change.
  • Support for multiple trigger events - Previously, you could only trigger on one event - for example - Create, or, Delete. Now, you can choose different permutations of events, such as Update or Delete or Create or Update or Delete.

Trigger with multiple events

We are also providing migration guidance for our customers, although there is no automatic migration at this time, which is available here. Finally, here's a list of the remaining features in automated flows that are not yet available but will be in the subsequent release wave:

  • Triggers based on certain attribute values: For example, trigger only based on records in a certain state. By including triggers in the middle of flows, you can leverage them as Wait conditions inside of a flow.
  • Call other flows: Flows can now call other flows and pass parameters to them.- Run As capabilities: Automated flows that are triggered by CDS for Apps can run with either an account defined by the owner of the flow, or with the identity of the user who performed the change that caused the trigger.
  • Resume flows from a failed action: If a flow fails on an action, makers can resume the flow right from that action once they’ve repaired the error.
  • Support for on-demand and event triggers in one flow: Flows can now both be automated (triggered by events in the system), and instant (triggered on-demand) at the same time.

Fixes and improvements

Note

No specific fixes or improvements have been publicly disclosed as a part of this released version