Close

Deploy Logic App via Portal

Another quick gotcha. If you want to migrate a Logic App from Development to Accept and you don’t want to use Powershell/ARM or Visual Studio Team Services (DevOps), you can perform the following steps in the Azure Portal: Clone the Dev version of your Logic App and name it Acc_LogicApp (follow the correct naming convention).…

Logic App parameters in SQL

In a previous post, I explained how you can use Logic App parameters in ARM templates. This solution is quite complicated. You will have to parameterize your Logic Apps. At deployment, the parameters are substituted by actual values. But, If you lookup the logic app in the Azure Portal, you will notice that the value…

Run After in Logic Apps

Using the visual designer in Logic Apps, you can specify the Run After property. Let’s say you have multiple branches and an action that should run after one of the branches has succeeded. Note that if one of branches is successfully executed, the other branches are skipped. That’s why you need a run after property…

Error Logic App: Workflow Parameter not found

I built a Logic App with the following action: “Email1_-_replace_siteUrl”: { “type”: “Compose”, “inputs”: “@replace(actionBody(‘HTTPGetEnquete’),'{{siteUrl}}’,parameters(‘customerSatisfactionSite’))” … I could successfully deploy the logic app, but on runtime I received the following error: Unable to process template language expressions in action ‘Email1_-_replace_siteUrl’ inputs at line ‘1’ and column ‘2730’: ‘The workflow parameter ‘customerSatisfactionSite’ is not found.’. I…

Import Logic App from Azure

I’m using Powershell to deploy my API Apps, Logic Apps and Azure Functions. Logic Apps can be developed in Visual Studio, but for deployment to Azure they need to be parameterized. The parameterized version of the Logic Apps is in my deployment folder, not in Visual Studio. Maintaining the Logic App in Visual Studio as…

Logic App error using workflow parameters

I received the following error when deploying a Logic App via Powershell/ARM: InvalidTemplate. Unable to process template language expressions in action ‘HTTP’ inputs at line ‘1’ and column ‘1420’: ‘The workflow parameter ‘ahakStorageConnectorName’ is not found.’. At the top of the Logic App Json file, I defined the parameters. The parameter values were contained in…

Deploy Logic App using Powershell and ARM

To deploy a logic app via Powershell, I used the following approach; Create a directory structure with two folders, i.e.: C:\Sources\PBaars\Deployment\Release1.5\AAA-DeployResources C:\Sources\PBaars\Deployment\Release1.5\ProcessPlanning Folder AAA-DeployResources contains reusable artefacts like a parameter file and a Powershell module with reusable code. In this case the reusable code uploads files for a Web App or API App to a…

Retry in Logic Apps

For easy reference this information is taken from the Microsoft Azure site. HTTP actions and API Connections (like the Azure Storage API, SharePoint API or child workflows) support retry policies.  A retry policy applies to intermittent failures (characterized as HTTP status codes 4xx (408, 429) and 5xx as well as any connectivity exceptions) and is described…