question

DanielKrantz-7993 avatar image
0 Votes"
DanielKrantz-7993 asked David-0467 edited

Logic App Standard with Transform XML shape

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

azure-logic-apps
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

When deepdiving in the logstream I found that Csharp scripts (from standard functoids) are not supported?!?

 statusCode='InvalidXsltContent', error='{"error":{"code":"InvalidXsltContent","message":"A runtime error occurred while transforming the given input with the provided map. Details: 'Compiling JScript/CSharp scripts is not supported'."}}'
0 Votes 0 ·

Hey @DanielKrantz-7993 - Sorry for the late response. With Logic Apps Standard, I believe you have to place your maps under Artifacts/Maps/Schemas folders, as documented here: https://docs.microsoft.com/en-us/azure/logic-apps/single-tenant-overview-compare#other-single-tenant-model-capabilities
Also, is the same XSLT working when running on the Consumption plan and Integration account?

0 Votes 0 ·

Hi @MikeUrnun ,@DanielKrantz-7993, Even I am facing the same issue with Logic Apps Standard. I have maps placed under Artifacts/Maps/Schemas folders, as documented here: https://docs.microsoft.com/en-us/azure/logic-apps/single-tenant-overview-compare#other-single-tenant-model-capabilities

Yes, the XSLT is working fine when running on Consumption plan and Integration account

0 Votes 0 ·

1 Answer

David-0467 avatar image
0 Votes"
David-0467 answered David-0467 edited

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.




5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.