You’re offline. This is a read only version of the page.
40
Hi everybody,
I've been thinking about this for a while now, and I'm curious to see what the community has to say. There are a couple of questions I have.
1. What are the strengths and weaknesses of the different options for calling the Web API?
2. Is Flows poised to replace a good deal of the operations now handled by plugins/custom workflows?
My thoughts so far are this: Javascript is useful for UI changes, especially insofar as it can be used in webresources. Plugins seem to be a less verbose way of implementing event-based triggers (CRUD). Flows seems to be a more limited way of addressing similar issues. It seems to me that the benefit of plugins & custom workflows is flexibility, but that their creation often requires external developers (in small companies) and once they are created they are difficult to maintain/update.
What do you all think? Strengths and weaknesses of the four? How much is Microsoft Flows going to change how small businesses manage their CRUD operations?
Hi there,
You are correct, javascript is a powerful tool for doing client side operations (calculations, ribbons, form operations). Using plugins you can integrate custom logic into the platform code, in order to suit your business needs. This however, will require development and testing and depending of the scale of the project it may take a while to implement.
Microsoft Flow (now Power Automate) aims to provide a friendly and intuitive way of creating custom business logic, without having to rely on creating custom code. It's great for small businesses since lots of business flows can be converted in order to be used and automated with Microsoft Flow (Power Automate).
Thank you!
Share
Report
All responses (
Answers (
