Any ways around xml size limits using renderToPdf? Running to this error: Error Parsing XML: The parser has encountered more than "100,000" entity expansions in this document; this is the limit imposed by the application.

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the error you're encountering is due to the XML parser encountering more than 100,000 entity expansions, which is the limit imposed by the application. This could be due to a large dataset being processed or a complex XML structure. One way to work around this issue is to simplify your XML structure or reduce the size of the dataset being processed. If your XML contains a lot of repeating tables or complex elements, consider simplifying these or breaking them down into smaller, more manageable parts. Another approach is to validate your XML before attempting to render it to PDF. There are many online tools available that can help you validate your XML and identify any potential issues. This can help you ensure that your XML is well-formed and does not contain any errors that could cause the parser to exceed its entity expansion limit. Also, it's worth noting that some users have reported issues with certain XML elements causing the PDF rendering to be truncated. In these cases, removing or modifying these elements resolved the issue. For example, one user reported that removing all of the pure-table classes from their XML fixed the problem. Finally, if you're using the

N/render

module to render your PDF, you might want to consider using the

N/xml

module instead. Some users have reported that this module is more reliable and less prone to errors when dealing with large or complex XML structures. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******