“Show me a ten-foot wall and I’ll present you an eleven-foot ladder” ― Peter Bevelin
Using Flow for information migration is simple however has limitations it is best to think about, these limitations could cause issues left the info migration in limbo, while ready for the api limits for every day and Flows waking up and working
When you hit the day by day restrict for Flows, they cease working till the following day (when restrict resets).
Considerations
- Data migration can have a number of data and will take many days
- Flows don’t fail, they queue them up
- The solely solution to cease Flows triggering is to delete them or put the Dynamics 365 setting into admin mode.
There are examples the place the Flow limits meant the Flows have been in a ready state for 4 days as a result of hitting the throttling restrict every day.
Flows are usually not simply on Flow runs by actions contained in the circulate.
How did we get right here with Flows
Microsoft initially had workflows which have been hosted by Microsoft and used Async service on the Dynamics 365 server. There have been no limits on workflows however from Microsoft’s perspective this isn’t nice as a result of these run on Microsoft sources and prices them to host and run them.
Microsoft created Flows, with larger performance and constructed on Logic apps. Flows are a scalable, enterprise resolution and with connections let you create Low code options and hyperlink techniques collectively.
The profit to Microsoft is the Flow runs are simply counted and Flows are hosted in Azure which is scalable. Microsoft pushed Dynamics 365 customers to make use of Flows and warn that workflows will likely be deprecated someday sooner or later. Flows permit Microsoft to estimate and management how a lot it prices to run Flows. Dynamics 365 on-line is a service, so Microsoft don’t wish to have limitless useful resource/compute for individuals.
Flows permit individuals to scale up and pay for what they use in basic Azure costing course of. This initially appears unfair as a result of we have been used to no limits however paying for what you employ is in the end truthful.
You get taxed a technique or one other with performance and it’s not one thing you’ll be able to resist. It’s vital to align your options with Microsoft’s highway map. If you resist and proceed to make use of workflows as a result of they’re free then sooner or later you’re creating an enormous upgrading process.
Flow first
I’ve a Flow first perspective and workflow mustn’t created on tasks going ahead. Many Dynamics 365 professionals resist this as a result of they’ve Workflow expertise and may not have created a circulate but. By default we don’t like change and keep on with what we all know.
Make them do it in a circulate, it is going to be sluggish to start out with however they are going to quickly begin to love Flows as a result of they’re extra highly effective
How to cancel flows
There isn’t any solution to bulk cancel flows, it’s a one after the other occasion. Flows queue up runs even when they aren’t enabled!! The solely solution to cease them is to delete them (and there’s no solution to bulk delete flows!!)
in the event you cancel a circulate it doesn’t cease the circulate working when the api threshold restrict is refreshed if you hit a brand new day.
It’s doable you would be left with 1000’s of cases of flows left in a working state, with you ready for refreshes of API limits. These might be days!
Deleting flows is simply a alternative when you have an answer with the flows in and extra really helpful with an automatic launch.
Logics apps?
Microsoft have created performance to run Logic apps in your native machine and a few discuss that we must always all be shifting to Logic apps. This mixed with an improved editor ought to make it simpler for no code professionals to create logic apps.
I’m undecided about this or if it’s the course of journey however for the time being Flows are simpler due to the present setting connection which means the Flow can work within the setting it’s in and is definitely deplorable.
What’s the same old information migration alternative
The frequent instrument I see used for information migration on giant tasks is Kingswaysoft. I haven’t used Scribe on-line however I imagine it has comparable performance, so it will depend on the experience of your crew.
Microsoft is shifting to rely the actions inside a circulate and step in a circulate will likely be an motion which you should have a restrict
Dynamics 365 and replicating to an SQL database for reporting
Flow restrict
The Flow restrict is a subject that may more and more come up in Dynamics 365 tasks, as extra tasks hit the restrict.
My feeling is the restrict is a bit low, notably contemplating the variety of environments you’ll be able to have in a big challenge.
Conclusion
Flows are superior and mixed with connections they’re powering the no/low code revolution in Dynamics 365/Power Platform tasks. Flows and Power Platform are changing the bespoke .Net functions and Excel spreadsheets that may develop in corporations.
Microsoft is beginning to be tighter with the Flow limits and charging extra sooner or later. This appears unfair as a result of we’re coming from not paying a lot however in reflection I are inclined to view the Azure/utilization pricing as truthful.
Currently the best way Flows have some odd methods of labor and the turning off performance could be a nuisance as a result of the runs are queued, ready for you flip the flows again on. The solely method spherical that is deleting the circulate.