Decoding Logic App Dilemmas: Using Storage Account, Azure Functions, and Logic Apps to merge mult...
Welcome again to another Decoding Logic App Dilemmas: Solutions for Seamless Integration! In this POC or dilemma, the goal we want to achieve is to merge
Friday Fact: Logic App Consumption and Standard have different Action name restrictions
By setting proper names for your actions, you can quickly identify what they are intended for and what they are doing without the need to enter each action to
Friday Fact: Parse JSON action input parameter (Content) supports the use of functions
When working with Logic Apps, it's often necessary to employ conversion functions in the form of expressions For example, you might need to convert XML to
Decoding Logic App Dilemmas: Using Event Grid to detect deleted files from Storage Account and tr...
Welcome again to another Decoding Logic App Dilemmas: Solutions for Seamless Integration! This time, we start this document by saying that, unfortunately, the
Logic App Consumption: How to set an API connection to use Logic Apps Managed Identity inside Vis...
Recently, we had a requirement to put some files into a storage account, and to do that, for security reasons, we had to use Logic Apps Managed Identity to
Friday Fact: Logic App Consumption and Standard name have different size limits and restrictions
Depending on the Logic App type you are using, Logic App Standard or Logic App Consumption, you will notice that each of them has different name size
Friday Fact: Logic Apps decode all sorts of Base64 files, but, sometimes, not the way you expect!
When you need to decode a Base64 file, you can rely on Logic Apps to do it, in concrete you can lean on an expression to help you achieve that To put it into
Friday Fact: Response Connector Do Not Perform A Schema Validation At Runtime: Workaround!
When you need to perform a schema validation in runtime while using the trigger, When a HTTP request is received, Logic Apps gift us the possibility to
Logic App Transformation Error: InvalidXml. The XML validation failed. Data at the root level is ...
In this saga of Errors and Warnings, Causes, and Solutions in Azure - if you follow me, you know that this is one of my favorite topics - I got a fancy one If
Friday Fact: It is possible to create an XML first-class experience inside Logic Apps.
By default, Logic Apps provides a good first-class experience for JSON, that means when we receive a JSON message, we can tokenize the elements by using a