Blog Post

Azure Integration Services Blog
5 MIN READ

.NET Framework assembly support added to Azure Logic Apps (Standard) XSLT transformations (GA)

KentWeareMSFT's avatar
KentWeareMSFT
Icon for Microsoft rankMicrosoft
Nov 07, 2022
This blog post is a collaboration between Praveen Srivastava (Principal Software Engineering Manager) and Kent Weare (Principal Product Manager) from the Azure Logic Apps team.   Update (03/03/20...
Updated Jul 13, 2023
Version 6.0
logic apps
daver64's avatar
daver64
Copper Contributor
Mar 10, 2023

Hi Kent,

 

Your suggestion helped solve the problem I reported above. I have to be honest I didn't include it as I thought the comment applied to public preview only and now this service is GA. Apologies I should have tried it.

 

However, the problem I now get when executing such a map is just simply 'BadRequest'. My colleague also got the same and added a scope (try catch pattern) and filtered for failed items which gave more information on the error which was "The .NET framework worker could not be found.".

 

I've tried a normal xslt 1.0 map that has no script blocks and even that gives 'BadRequest'. If however I take out the "AzureWebJobsFeatureFlags": "EnableMultiLanguageWorker" my normal map works and then of course my map I really want to test gives the error that I previously reported.

 

So it appears adding "AzureWebJobsFeatureFlags": "EnableMultiLanguageWorker" causes a problem for all maps. I assume then it's down to an extension issue as it may think the above is not a valid option??

 

Many thanks

 

Dave