Known Limitations in Server-Side Dynamic Rich Texts, Hyperlinks, and Images

Doesn't support:

• Microsoft PowerPoint.
• Copy and paste of content into a rich text field. You must manually enter the content.
• RTB tokens in non-formatted clauses.
• RTB tokens within bullets in a document template.
• Templates designed by using Microsoft 365 editor.
• Contract editing if the document was generated by using a document template with RTB tokens directly in the Microsoft 365 editor.
• User-input text that contains special characters such as less-than (<) and greater-than (>) signs. These characters are interpreted as HTML tags, or errors.
• Images in rich text fields, if the Encrypt Files and Attachments platform encryption is enabled.
• RTB tokens placed within a paragraph. It causes the document generation to fail.

Doesn't support:

• Hyperlink format, such as a blue color in the generated PDF file.
• Templates designed by using Microsoft 365 editor.
• Contract editing if the document was generated by using a document template with RTB tokens directly in the Microsoft 365 editor.

Dynamic Images

Dynamic Images in Server-Side Document Generation

Doesn't support:

• Image rotation in .docx and .pptx files.
• Images stored in external repositories.
• Loopover images in .pptx document templates.
• Image size greater than 4.9 MB.
• Images stored in multiple repositories to render in the same generated document.
• Image URLs in the dynamic image field. Omnistudio Data Mappers can't pass the image URL for an image. You must provide the sObject Id or the name of the image in the image field.
• WebP image format
• RTB image resizing
• Multiple IMG tokens within the same text box boundary in a Microsoft PowerPoint file. Document generation fails when a single text box contains more than one IMG token.
• Images stored under static resources are not supported in the Server Side Document Generation (through Omniscript or Apex Code or IP).