Referencing a richtext field in an Advanced PDF template causes XML parsing errors when it encounters a tag with an attribute whose name contains dashes, like <i data-my-attribute="thingy">Some text here</i> How do I prevent the error from making the PDF render fail?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that the issue you're encountering is due to the XML parser not being able to handle certain characters in the rich text field. This is a common issue when dealing with XML and HTML content. To prevent the error from making the PDF render fail, you can use the Freemarker's escape mechanisms. Freemarker has a built-in function for escaping XML, which can be used to escape the problematic characters in your rich text field. Here is an example of how you can use it:

freemarker
${yourRichTextField?xml}

This will escape all the problematic characters in the

yourRichTextField

field. However, be aware that this method is deprecated because it can lead to double escaping, especially since the standard rendering by NetSuite actually does its own escaping. Another approach is to manually replace the problematic characters. For example, if the problematic character is '&', you can replace it with '&' in the PDF template:

freemarker
${yourRichTextField?replace("&","&")}

This will replace all occurrences of '&' with '&' in the

yourRichTextField

field. Remember that you need to be careful with this approach, as you don't want to replace every character, only the ones being used as values. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******

This doesn't concern any of the characters escaped by the ?xml built-in.