Adam, I completely agree. I do not see how Flow will be able to replace native workflows because there are use-cases for synchronous workflows that Flow cannot do. I prefer to work with Azure LogicApps becuase it can do what Flow does for a fraction of the cost. When they advertise 2000 "runs", that is actually each step in the Flow that interacts with CRM, not a single execution of a Flow. For example, If you have a single Flow that has 10 action steps that access D365, then you have 10 runs each time you run that flow.
------------------------------
If this answered your question, please click on the arrow button next to Reply Inline and choose 'Make Best Answer.'
Thanks.
Nelson Johnson, Solution Architect
BroadPoint, Inc., Bethesda MD
Link with me!
https://www.linkedin.com/in/nelsonjohnson/------------------------------
Original Message:
Sent: Aug 05, 2019 09:56 AM
From: Adam Posegate
Subject: Workflows now suggesting I use Flow
This morning I started seeing this message when I edit workflows:
- Flows are owned by a user, while workflows can be set to any owner. I want the workflow to be run by a system user or user who initiated the workflow.
- Flows require syntax knowledge in order to accomplish the same action in a comparatively simple approach using dropdown selections.
- Flows do not "port" existing workflows. If I am using a plugin or workflow toolkit, it is prohibitive to attempt to recreate this using flow.
Flow was pitched as a "no cliff" approach to automation at the CRMUG Summit last October, with complete parity to workflows. As far as I can tell, the development of a more pleasing graphical interface was done without regard for the fact that actually using workflows is easier.
------------------------------
Adam Posegate
Fox Valley Technical College
Appleton WI
------------------------------