> 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/news/2025/pdf-files-in-reports.md).

# PDF files embedded in reports

Insert PDF documents directly into your Daxium-Air reports using the file attachment field and the FileImage function.

**Published on October 8, 2025**

![](https://1160383192-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FotkY8NZEogvR3XMRPSkn%2Fuploads%2Fgit-blob-519d666a47024e0e8a647ede719f7e9ac4de6770%2F22a93a_c17bcdaec0074693a92edef5dd8f84b3~mv2.png?alt=media)

Good news for fans of comprehensive reports — Daxium-Air now lets you embed your PDF documents directly into your reports.

## File attachment field in reports

Thanks to the **file attachment** field, you can automatically insert a preview of the PDF pages into your reports, using the `FileImage` function.

Example syntax:

```
<%FileImage('Fichier', 'All', 600)%>
```

Your PDF is then displayed directly in the report, page by page. Ideal for attaching a contract, an intervention report, or supporting documents.

{% hint style="info" %}
Check out the [Reporting](https://www.center.daxium-air.com/user-documentation/build/building-the-platform/building-the-reporting/) documentation to learn more.
{% endhint %}


---

# 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/news/2025/pdf-files-in-reports.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.
