The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Microsoft future vision is making it easier for every business to transform how people work in their Office 365 Ecosystem. Microsoft Flow is one of the services which will help businesses to get more productivity across various online services and platform.
These days while creation of Dynamics CRM Workflow, you might have noticed the below Notification from MS: "We recommend using Microsoft Flow instead of background workflows"
What does it mean?
In future we might have to take approach of a MS Flow as a first design. That is, any new asynchronous transaction with D365 CRM we have to approach the solution with Flow first, and if it doesn't fit, we need to fall back to Workflow.
In future MS Flow might be a vital component of Dynamics CRM Solution. So, thought of to write a blog which can tell us when to go for Dynamics 365 Workflow and Microsoft Flow.
A Dynamics CRM consultant knows what Microsoft Workflow is (both Asynchronous and Synchronous). However, still only few of us are using Microsoft Flow applications with Dynamics CRM.
Microsoft Flow is Microsoft’s online service that automates workflows across multiple web-based services platform. These services include Microsoft services like Dynamics 365 CRM, SharePoint, OneDrive, OneNote, Office 365 (Excel Online) and others, as well as many third-party services, like Twilio Messaging, Google Drive, WordPress, SurveyMonkey, third party email services (Gmail, Outlook.com etc), and even Facebook, LinkedIn social media platforms. The applications of MS Flow is infinite :-) , however, for your business process before selecting MS Flow or Dynamics CRM traditional workflow there are some key points which I will try to cover below.
In short, Microsoft Flow lets us create specific actions based on trigger events.
Technical reasons to use MS Flow:
Some of the applications of MS Flow:
1.1) Push notifications: If you install the Flow app on your mobile device, you can create flows that give you a mobile push notification when a Dynamics 365 events happen and that is assigned to you. This you can use for approval process.
1.2) SMS Text Notification using Twilio connector
1.3) Email Notifications
Think in this way you can expose a Dynamics CRM Action which other system can consume through WebAPI call and this Action you can schedule in recurring manner to process bulk data records in System.
"Basically, Flow helps to talk between two systems easily and the applications are infinite"
Disadvantage (Over usage of MS Flow):
I am sure Microsoft will improve Flow and many more future will be added to this platform. I will be keep updating this blog based on MS changes.
Kindly give you comments and feedback so that I can improve this blog.
Business Applications communities