Welcome back to another edition of Friday Fact! Today, our fact is going to be an existing issue (bug) or a feature by design that somehow has to be changed for the existing BizTalk Logic App Adapter to work correctly. Luckily for us, this has no impact whatsoever on the Logic App Connector, so we will still be able to call our child Logic Apps.
You know that the legacy Logic App designer will retire and become unavailable at some point. It was supposed to be removed starting September 2024, but luckily for us, it is still here.
Saying that, what I recently found was that while creating a Logic App Consumption with When a HTTP request is received trigger, this trigger will have different behaviors with regards to the HTTP URL generated when we save the Logic App depending on if you are using the Legacy Design or the Generally Available Designer. And that will directly impact the BizTalk Logic App Adapter in BizTalk Server.
If you use the Generally Available Designer when you save the Logic App, the HTTP URL has the following structure:
- https://<prefix>.westeurope.logic.azure.com:443/workflows/<workflowID>/triggers/When_a_HTTP_request_is_received/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers%2FWhen_a_HTTP_request_is_received%2Frun&sv=1.0&sig=<secret>
Notice that the trigger name is: When_a_HTTP_request_is_received.
Now, if you use the Legacy Design to create the exact same Logic App, the HTTP URL has the following structure:
- https://<prefix>.westeurope.logic.azure.com:443 /workflows/<workflowID>/triggers/manual/paths/invoke?api-version=2016-10-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=<secret>
Notice that the trigger name is: manual.
Now again, from a Logic App perspective, this different behavior does not impact us to call child Logic Apps, nor with the:
- Legacy Designer
- Generally Available Designer
- or using the Legacy Designer inside Visual Studio
All of them will be able to recognize those Logic Apps Consumption.
However, the same will not apply to BizTalk Server Logic App Adapter. The adapter will be able to identify the Logic App:
but will fail because of the length of the HTTP URL.
Of course, this is a bug of the BizTalk Server Logic App Adapter caused by this different behavior of the Logic App Designer, which will block us from creating specific hybrid solutions in a fashion way.
To lazy to read? We’ve got you covered! Check out our video version of this content!
I hope you find this helpful! If you liked the content or found it helpful and want to help me write more content, you can buy (or help buy) my son a Star Wars Lego!
