Good day to all! we looked at some of the uses for Power Automate. In this article, I would like to dwell on some scenarios for using Logic Apps and a number of differences from Power Automate. As we found out earlier, Power Automate and Logic Apps are twin services that differ only in the location area (Office 365, Azure), as well as in the licensing approach and some internal features. Let's see today what features Logic Apps has, unlike Power Automate. Let's not waste time.
1. Frequency of triggers
There is no way in Power Automate to configure how often trigger conditions are checked. You have to rely on the default value. Logic Apps has the ability to customize the interval and frequency of the trigger check, which greatly speeds up the processing of events. However, Power Automate often has significantly fewer settings for triggers than Logic Apps:
Power Automate trigger "On item creation":
Logic Apps Trigger "On Item Creation":
In Logic Apps, for this trigger, there are also settings for the time zone and start time.
2. Switch between flow display modes
Logic Apps, unlike Power Automate, has the ability to switch between Design View and Code View. This feature is very helpful in debugging threads, and also allows you to make more subtle changes to the flow logic:
3. Debugging Threads
Often, when setting up flows, we need to check the correctness of the execution of one or another logic that was embedded in them. And here we can not do without debugging. Logic Apps has an incredibly handy thread debug mode that lets you display the input and output of each thread activity. Using this mode, you can at any time see at what stage what information arrived in the activity and what turned out to be the output of the activity:
In Power Automate, this mode is present, but in a very truncated version.
4. "Premium" connectors
As we already know, in Power Automate there is a division of connectors by type, into regular and "premium":
Regular connectors are always available, "premium" connectors are available only when you purchase a separate plan for users or streams. In Logic Apps, all connectors are available for use at once, but billing is carried out as the connectors are used. Executing regular connectors in a thread is cheaper, "premium" is more expensive.
5. Starting a thread on a button
And here Logic Apps loses to Power Automate in that the Logic Apps flow cannot be started, for example, by a button from the Power Apps application. With Power Automate, as we found out , you can create flows and connect them to the Power Apps application, for later call, for example, when you click on a button in the application. In the case of Logic Apps, if you need to implement such a scenario, you have to come up with various outputs, for example, use the βWhen receiving an HTTP requestβ trigger and send a request from the POST application to a pre-formed address:
6. Create a flow with Visual Studio
Unlike Power Automate, Logic Apps flows can be created directly through Visual Studio.
You can create and edit Logic Apps flows, for example, from Visual Studio Code if you have the Azure Logic Apps extension installed. After installing the extension, you will be able to connect to Azure. And after successful authorization, you will get access to the existing Logic Apps flows in this environment and you can proceed to editing the required flow:
Of course, I did not list all the differences between these two products, but I tried to highlight those features that caught my eye as much as possible when developing flows using Power Automate and Logic Apps. In the following articles, we will look at interesting features and implementation cases with you using other products of the Power Platform line, and we will return to Logic Apps more than once. Have a nice day, everyone!
Source: habr.com