Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Case documents error messages

Updated on March 29, 2022

Resolve any issues when you generate case documents by understanding the error messages. Inline error messages that an output document displays might help you locate and fix the issue.

The following table lists the error messages that are associated with case document generation, with explanations:
Error messageDescription
ERR_SKIP_HTML_IN_TABLEA table cannot contain content from a section, correspondence, a rich text editor, or HTML.
ERR_SKIP_HTML_IN_HEADER/FOOTERA header or footer cannot contain content from a section, correspondence, a rich text editor, or HTML.
ERR_RETRIEVING_HTMLA document cannot retrieve HTML from a section or correspondence.
ERR_INVALID_CONFIGURATIONThe JSON configuration is invalid.
ERR_INVALID_TYPEThe JSON type key is not a property, attachment, section, or correspondence.
ERR_EMPTY_PROPERTY_NAMEThe JSON name key is empty.
ERR_SKIP_ATTACHMENT_IN_PARAA document cannot contain an attachment in a paragraph with text.
ERR_INVALID_ATTACHMENT_INFOThe JSON configuration is correct but the attachment keys are invalid.
ERR_SKIP_NON_IMAGE_ATTACHMENT_IN_TABLEA table cannot contain non-image attachments.
ERR_SKIP_NON_IMAGE_ATTACHMENT_IN_HEADER/FOOTER A header or footer cannot contain non-image attachments.
ERR_COULD_NOT_ADD_ATTACHMENTAn application could not add an attachment to a document.
ERR_ATTACHMENT_NOT_FOUNDAn application could not find an attachment that matches a provided key.
ERR_ADDING_IMAGEAn application failed to add an image to a document.
ERR_PROCESSINGAn error occurred during processing of HTML or an attachment.
ERR_PAGELIST_UNSUPPORTEDA document does not support page lists outside tables.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us