question

TommyTam-4623 avatar image
0 Votes"
TommyTam-4623 asked MayankBargali-MSFT edited

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

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!?134446-untitled.png


azure-logic-apps
untitled.png (29.4 KiB)
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.

1 Answer

MayankBargali-MSFT avatar image
0 Votes"
MayankBargali-MSFT answered MayankBargali-MSFT edited

@TommyTam-4623 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.

· 2
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.

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.

0 Votes 0 ·

@TommyTam-4623 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

0 Votes 0 ·