azure-logic-apps

I'm trying to read the content body of a message in an Azure Logic App, but I'm not having much success. I have seen a lot of suggestions which say that the body is base64 encoded, and suggest using the following to decode: @{json(base64ToString(triggerBody()?['ContentData']))} The base64ToString(...) part is decoding the content into a string correctly, but the string appears to contain a prefix with some extra serialization information at the start: @string3http://schemas.microsoft.com/2003/10/Serialization/�3{"Foo":"Bar"} There are also some extra characters in that string that are not

I was experiencing a problem with a logic app which Used the Create SAS URI by path action to get a SAS-enabled URL for a blob in a storage account Used the SFTP copy file action to copy the file to an SFTP connector The process would fail roughly 50% of the time with an authorization error when trying to fetch the blob from storage. "actions": { "Create_SAS_URI_by_path": { "inputs": { "body": { "Permissions": "Read" }, "host": { "connection": { "name": "@parameters('$connections')['azureblob']['connectionId']" } }, "method": "post", "path": "/datasets/default/CreateSharedLinkByPath", "queries

I am new to Azure logic apps. I have a service bus and pass a json object message to that service bus then I set up an action in logic apps to listen to my service bus. So everytime a new message come in to that service bus my logic apps will pick it up and send it to http. My question is how can I grab the property from the message in service bus and pass it to my http action. I tried this “Id” : “@{json(triggerBody()[‘ContentData’]).id}” but it's not working Who and how is sending the message on the queue? I read a json message property (DestinationPath) in this way: @{json(base64ToString

Can you have automated regression/integration tests for Azure Logic Apps? And if you can, how? ... especially in the context of CI/CD builds and deployments ... and if you can't, why not!! There isn't any out-of-the-box tooling yet to provide automated testing of Azure Logic Apps. We have a few customers who have followed one of the following patterns. There is also this article that goes into detail on how to create a Logic App deployment template: After deployment (using a release management tool like Visual Studio Release Management), a series of unit tests are run (writtin in something

I am doing on POC for getting records from On-Premise SQL By using Logic Apps + API Apps. I have created SQL Connector in API Apps and also created Logic Apps. But when try to add the SQL Connector API App in Logic App Designer. it is saying Failed to fetch swagger. Ensure you have CORS enabled on the endpoint and are calling an HTTPS endpoint. I browsed and found out for setting the Permission Level. Appsettings - > Set API Definition & CORS enabled. Authentication/Authorization - > On -> Allow Request (noAction) Restarted the API Service. but still getting the same error. I have browsed the