> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/build/building-the-reporting/report-templates/ppt.md).

# PowerPoint

Create PowerPoint report templates for visual presentations of field data.

PowerPoint (.pptx) templates let you generate visual presentations directly from your submission data.

## Overview

|                   |                                                                    |
| ----------------- | ------------------------------------------------------------------ |
| **Format**        | `.pptx`                                                            |
| **Report engine** | Aspose Library for PowerPoint                                      |
| **Best for**      | Visual presentations, slide-per-submission outputs                 |
| **Listing mode**  | Not applicable — one slide per related submission via `Relation()` |

## Configuration

The PowerPoint report feature is accessible from the report section, just like Word and Excel formats.

In **Report Engine**, select **Aspose Library for PowerPoint**:

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-de4d8bd898cde5de8300af07080fbde425c9e9c7%2F99cb50_ea5335cc669e4091b0176381f339fba2~mv2.png?alt=media)

Upload your document template in .PPTX format:

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-0b58952f44b60fb77bd770923582c027bd4290a2%2F99cb50_4b808a3f8be9490882b2c0864ccfa012~mv2.png?alt=media)

Once configured, the report template is accessible from your submissions like any other format. From the manual generation interface:

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-92a8d05fdb97639c2829a9105ed30c9e4d020dcb%2F99cb50_d66c6b08429c465b9dfe21885c180d1b~mv2.png?alt=media)

You can download the generated report from the notification bell or from the report access menu on the submission.

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-b75605be6f2e77e5c19db03e9ef6dab3e47aacba%2F99cb50_619e83b1f666462c96dcfbf89dfa3a82~mv2.png?alt=media)

## Field syntax basics

The syntax is similar to the [Word report type](/user-documentation/build/building-the-reporting/report-templates/word.md). However, fewer options are available. For the full reference, see [Syntax & Functions](/user-documentation/build/building-the-reporting/syntax-functions.md).

### Inserting fields

Same syntax as Word:

`<%[FieldName]%>`

### Supported functions

In text boxes and table cells, you can use: **If**, **Format**, **Date**.

### Images

Simple image insertion — no size options. The image is resized to fit the corresponding text box or table cell:

`<%Image([ImageFieldName])%>`

## Relationships

You can insert a relationship into your presentation. Create a section with the following syntax:

`<%Relation:RelationFieldName;Name:SectionName%>`

* *RelationFieldName* — system name of your relation field
* *SectionName* — an arbitrary name for your PowerPoint section

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-c54274cee44d53a68fcb93dd469ac229fadd606f%2F99cb50_227185889b6b46fe910cb41f8adf4840~mv2.png?alt=media)

One slide is created per related submission — the template slide is replicated for each.

{% hint style="warning" %}
Only **1 level of relation** is supported.
{% endhint %}

## Tips

### Quotes in expressions

If you insert text values into function arguments, apostrophes must be straight single quotes `'`. PowerPoint sometimes automatically converts them to curly quotes `'`. Prepare function strings in a text editor first, then copy/paste them into PowerPoint:

`<%If([Image2.Count]>0,[Image2#1Comment],'N/A')%>`

### Text placement

No text should be added after closing an instruction with `%>`. If you need to add text on the same slide, place it in a separate frame.

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-4345b29e724e5d6948b323cfb6570776d94ec201%2Fdda3d7_dd2133506f9741fc85748ff2d54fd3c4~mv2.png?alt=media)

## Limitations

* Format: `.pptx` only.
* **Hide/End**, **Display/End**, and **Images** (multiple) functions are not supported.
* Images have no size parameters — dimensions are determined by the placeholder frame.
* Only 1 level of relation nesting is supported.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.center.daxium-air.com/user-documentation/build/building-the-reporting/report-templates/ppt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.