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

# Fichiers PDF intégrés dans les rapports

Insérez des documents PDF directement dans vos rapports Daxium-Air grâce au champ pièce jointe et à la fonction FileImage.

**Publié le 8 octobre 2025**

![](https://content.gitbook.com/content/IoML9Vb5SQHzcBvJjYc2/blobs/qFr7QVzYm4GgJOCY6pLH/22a93a_c17bcdaec0074693a92edef5dd8f84b3~mv2.png)

Bonne nouvelle pour les adeptes de rapports complets — Daxium-Air vous permet désormais d'intégrer vos documents PDF directement dans vos rapports.

## Champ pièce jointe dans les rapports

Grâce au champ **pièce jointe**, vous pouvez insérer automatiquement un aperçu des pages du PDF dans vos rapports, en utilisant la fonction `FileImage`.

Exemple de syntaxe :

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

Votre PDF s'affiche alors directement dans le rapport, page par page. Idéal pour joindre un contrat, un compte-rendu d'intervention ou des pièces justificatives.

{% hint style="info" %}
Consultez la documentation [Reporting](https://www.center.daxium-air.com/user-documentation/documentation-utilisateur/build/building-the-reporting/) pour en savoir plus.
{% 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/nouveautes/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.
