I'm trying to convert a CSV to XML using Logic App, which had always worked fine until I recently hit a size issue, don't even know what the size limit is. Anyone have any idea!?

@Tommy Tam Internal size limit for the XML transform action is 100MB. The XML from the trigger is base64 encoded and some content gets added for transform , so the final size gets increased. Note: If your file is smaller ~70MB then also you might observe the same issue as mentioned above as it is base64 encoded and some content gets added for transform. There is no option to increase the size limit of the connector, to workaround try splitting the XML into multiple files of smaller size (< ~60MB) and process.

Transform XML - The page was not displayed because the request entity is too large

Accepted answer

MayankBargali-MSFT 68,476 Reputation points

2021-09-23T03:38:25.637+00:00

@Tommy Tam Internal size limit for the XML transform action is 100MB. The XML from the trigger is base64 encoded and some content gets added for transform, so the final size gets increased.

Note: If your file is smaller ~70MB then also you might observe the same issue as mentioned above as it is base64 encoded and some content gets added for transform.

There is no option to increase the size limit of the connector, to workaround try splitting the XML into multiple files of smaller size (< ~60MB) and process.
Please sign in to rate this answer.
Tommy Tam 21 Reputation points

2021-09-23T21:56:36.58+00:00

What if splitting is not an option as the entire XML output has to all be in one file? I've read somewhere that Azure functions can be a workaround but I can't find any examples to do that with the already existing schema and mapping files I created using BizTalk.

MayankBargali-MSFT 68,476 Reputation points

2021-09-24T04:01:38.297+00:00

@Tommy Tam For function you need to write your custom code for the transformation. But the HTTP request length is also limited to 100 MB (104,857,600 bytes), and the URL length is limited to 4 KB (4,096 bytes). These limits are specified by the httpRuntime element of the runtime's Web.config file as mentiond in this document.
You can refer to this discussion previously for the workaround.

I do see AzureFunctions XSL Mapper sample created in github repository but if you are using function then you can still hit the 100 MB limit and the workaround would be switch to using a custom site extension (or for linux, with a custom container) where you can modify the web.config
Sign in to comment

Transform XML - The page was not displayed because the request entity is too large

0 additional answers