Logic App Standard with Transform XML shape

Question

We're experiencing problems with the XSLT-maps created with the Enterprise Integration Tooling for VS2019 (and 2015) on Logic Apps Standard. The maps are working fine and just as expected when there are no functoids involved but as soon as there are functoids such as the "string concate" the XSLT will contain an import of https://.../functoids/functoidsscript.xslt. This will result in an "invalidXsltTransform" error message in the XML Transform shape.
I recognize the problem from the early days of Integration Account but I'm out of ideas on how to fix this. Anyone who encountered the same problem and might have a solution?

Best Regards,
Daniel

Answer 1

I suspect the issue here is because the Logic Apps CP+IA XSLT Transformation runs in a sandbox, i.e. it is hosted in a separate Azure Web Apps environment and therefore isolated, whereas the Logic App Standard runs within the workflow. The issue is a bit like the Inline Script action where certain JavaScript libraries cannot be referenced.

The issue is currently under review, but at the moment it means virtually no BizTalk map will work. The only ones that will are those with direct field mapping and only use the following functoids:

• all the Advanced Functoids except the Scripting Functoid;
• the Inline XSLT, Inline XSLT Call Template script types of the Scripting Functoid;
• the isNil Logical Functoid.

Until the issue is resolved a workaround would be to write an Azure Function to perform the transformation.