Original Post is here.
In Logic Apps and Flow, patterns for error handling are available. For those who write the program, it is a familiar Try-Catch-Finally format.
Original Post is here.
In Logic Apps and Flow, patterns for error handling are available. For those who write the program, it is a familiar Try-Catch-Finally format.
Original post is here.
I attempted to retrieve the execution history of Logic Apps and tried to see if I could see the date and time that I processed recently.
ORiginal Post is here.
Although I was doing various templates to distribute Logic Apps including API connection, I tried collecting it as a memorandum because I took a lot of trouble in rewriting the point and Template when distributing it.
This entry was made with reference to Sacha Bruttin 's wonderful entry. Deploy Logic Apps & API Connection with ARM https://www.bruttin.com/2017/06/13/deploy-logic-app-with-arm.html
Original Post is here.
For some reason I created LogicFlow to register accounts. However, there was a problem of what to do with the initial password. Although it seems likely to go easy without using Azure Functions, I decided to do it with Logic Apps.
In the past update, the IF connector of Logic Apps was updated and it was easy to describe it even in a newly nested state. There was a mistranslation of Japanese, but it is very easy to deal with multiple judgment conditions. However, unlike conventional IF connectors, the description method is not automatically updated. In order to update this, we need to change the description directly in CodeView, so summarize the rewriting method.