It is connected to the Common Data Service (CDS) behind the environment it is running in. When a record is selected – this is the first event in the Flow and this Trigger allows the Flow to appear in the Flyout.Here is what the Flow looks like (if it looks a little scrunched on your screen, click on it to get a bigger view): We will use the 3rd party service Twilio and other existing standard connectors to execute this process. The business scenario is that you want to be able to send a broadcast Text Messages (SMS) to Contacts on a Marketing List. I will show you a Flow that a user can run from within Dynamics 365. Note: in a future blog post I will explain how you can get around this limitation of only displaying Flows using ‘when a record is selected’ trigger. Additionally, as you would suspect the Flow has to be enabled before it will appear. Button Flows, Recurrence Flows or Flows that start with any other trigger type will not appear in the Flyout. Only Flows that start with the COMMON DATA SERVICE TRIGGER WHEN A RECORD IS SELECTED will appear in the Flyout. Here is the main piece of information you need to know.
Microsoft dynamics ce how to#
If you go to the online docs and search for embed Flow in Dynamics 365 you will either get a page that shows you how to enable the Flow button for Dynamics 365 or another doc that sort of explains how to get a Flow to appear in the flyout menu within Dynamics 365.īut unfortunately, they are skimpy at best and in the case of the second document listed, a little incomplete at best or a little incorrect as of the writing of this blog. Unfortunately, there hasn’t been enough information published about how to set this up and do it. Wouldn’t it be great if you could trigger a Microsoft Flow from within Microsoft Dynamics 365 CE? Well, we have been able to do that since V9.0 release.