# PPTX Rendering Considerations S-Docs PPTX templates use Microsoft PowerPoint files as the slide layout source. That approach gives you slide-native formatting and generated `.pptx` output. It also has a few important considerations to plan around. ### Key considerations * PPTX layout and styling come from the uploaded PowerPoint file. * Dynamic content only renders where valid S-Docs Microsoft template syntax is inserted. * PPTX merge fields, logic blocks, and query blocks must use square brackets. * Repeating tables must be built as PowerPoint tables. * The upload path and generation path must match. * Changes made in PowerPoint do not apply until you re-upload the file. * Related list tables cannot span multiple slides. * Some template features are not available in PPTX output. * Test slide overflow, images, and table output with real data before rollout. ### Not currently available These PPTX capabilities are not currently available: * Live Edit for generated PPTX documents * template headers and footers * component templates * S-Sign ### What to avoid Avoid these patterns in PPTX templates when possible: * fields or tags missing square brackets * mismatched upload and generation methods * repeating content outside a proper PowerPoint table structure * copying complex tables from external files without rebuilding them * packing too much dynamic content into one slide * editing a PowerPoint file locally without re-uploading it Simple slide-native layout is usually the safest choice. ### PowerPoint and template structure PPTX templates are built in Microsoft PowerPoint, not in the template body. S-Docs merges data into the uploaded `.pptx` file at generation time. That means slide structure, spacing, text boxes, images, and table layout should be controlled in PowerPoint. S-Docs logic still works in PPTX. The wrapper changes. Use square brackets around visible merge fields and Microsoft template markup blocks. {% hint style="warning" %} If a PPTX field or logic block prints as plain text, check the square brackets first. {% endhint %} ### Upload mode and generation path PPTX behavior changes based on your S-Docs version and whether **Enable New Microsoft Template Upload** is checked. If **Enable New Microsoft Template Upload** is checked: * this applies to Summer 2025 (`v10.0`) and later * the template is uploaded through the newer Microsoft template upload flow * the template can be generated through **S-Docs LWCs** or the **SDK** * the template is not compatible with the legacy custom S-Docs button If **Enable New Microsoft Template Upload** is not checked: * this applies to older templates and legacy upload flow templates * the template is uploaded through **Template Editor** * the template can be generated through the legacy custom S-Docs button * the template is not compatible with **LWCs** or the **SDK** Starting in Summer 2025 (`v10.0`), the newer PPTX flow uses Salesforce Compression functionality. That improves consistency, file handling, and performance in the newer upload flow. {% hint style="warning" %} If the upload method and generation method do not match, the PPTX template may appear valid but still fail to generate where you expect. {% endhint %} ### Table and repeating content considerations PPTX related lists render inside PowerPoint tables. Use a table with: * a header row * an odd row * an even row S-Docs uses the odd and even rows as the repeating pattern. If the table structure is incomplete, the output can repeat incorrectly or fail to render as expected. PPTX related list tables also cannot continue onto another slide. If one table can outgrow a slide, use `LIMIT` and `OFFSET` to split the data across slides or reduce the row count. If a related list only populates the first cell, check these first: * rebuild the PowerPoint table from scratch * simplify table styling, especially border styling * move the table to a simpler slide with fewer dynamic elements ### Feature differences from DOCX and PDF templates PPTX output is not the same as DOCX or PDF output. Use PPTX when you want presentation-style slides and PowerPoint-native design tools. Do not expect document-style features to carry over. For example: * PPTX does not support template headers and footers * PPTX does not support component templates * PPTX uses PowerPoint tables instead of HTML or Word table layout * PPTX formatting comes from PowerPoint, not CSS-driven page markup ### Best practice Build PPTX templates like presentation slides first. Then layer S-Docs syntax into that structure. Use: * PowerPoint-native layout and formatting * bracketed PPTX merge syntax * simple PowerPoint tables for repeating rows * real-data testing before release Test early if your template includes: * related list tables * conditional sections * embedded images * dense text that can overflow a slide * long lists that may exceed one slide ### Troubleshooting tip When a PPTX file fails or renders incorrectly, check these first: * missing square brackets around PPTX syntax * unsupported features such as components or Live Edit * upload mode and generation path mismatch * repeating content placed outside the required PowerPoint table structure * slide content that exceeds table or slide limits * a newer local file that was never re-uploaded If a table behaves unpredictably, test the same pattern in a smaller deck first. That helps confirm whether the issue is in the syntax, the PowerPoint structure, or the upload path. ### Related resources * Review [PowerPoint (PPTX)](/sdocs/template-architecture/document-formats/pptx-format.md) for format guidance and build patterns. * Review [Build and Upload a PPTX Template](/sdocs/template-architecture/document-formats/pptx-format/build-and-upload-a-pptx-template.md) for syntax, upload flow, and examples. * Review [Troubleshoot PPTX Generation](broken://spaces/WKNnJmhJBQwhdk5WBFsi/pages/oHOjBkHQcTceCbxsE9iL) for setup checks and failure patterns. * Review [Merge Fields With Microsoft Templates (DOCX, PPTX, XLSX)](/sdocs/template-architecture/inserting-merge-fields/merge-fields-with-microsoft-templates-docx-pptx-xlsx.md) for bracketed Microsoft template syntax. * Review [How to: Create a Table In Microsoft Templates (DOCX, PPTX)](/sdocs/advanced-template-logic/related-lists/how-to-create-a-table-in-microsoft-templates-docx-pptx.md) for table wrapper setup. * Review [S-Docs Limitations](https://kb.sdocs.com/knowledge-base/sdocs/understanding-template-formats/s-docs-limitations/) for broader product limits. * Review [PPTX Templates](https://kb.sdocs.com/knowledge-base/sdocs/understanding-template-formats/pptx-templates/) for additional PPTX background. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.sdocs.com/sdocs/template-architecture/document-formats/pptx-format/pptx-rendering-considerations.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.