If your organization uses Logic Apps Consumption for some of its enterprise integration scenarios, developing them inside Visual Studio 2019 is mandatory. There is no other way to apply proper CI/CD and source control to Logic Apps Consumption.
Although we basically have a browser embedded in Visual Studio to be able to access the Logic App Designer, the Logic App Designer within Visual Studio 2019 has some different behaviors than in the Azure Portal. One of these different behaviors is the fact we will reference here today.
If we are constructing a JSON payload inside a Compose action, notice that the Compose action inside Visual Studio sometimes doesn’t validate if the JSON payload is valid or not!
Notice that on the picture above is missing a comma between param1 and param2.
Worse, even if it validates and presents the error message in the editor, it will allow you to save and deploy the Logic app successfully with this error, but it will fail when we try to execute it.
This is the opposite of what happens inside Logic App Designer in the Azure Portal. Although it sometimes takes a little time to validate and present the valid JSON error message, you will not be able to save it if that payload is invalid.
This behavior is clearly a bug within the Visual Studio Logic App extension that I hope Microsoft will fix in the future since it may cause several problems in our processes, becoming a tedious and time-consuming task for analyzing the issues and their corrections.
To lazy to read? We’ve got you covered! Check out our video version of this content!
Hope you find this helpful! If you enjoyed the content or found it useful and wish to support our efforts to create more, you can contribute towards purchasing a Star Wars Lego for my son!
