> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/fr/troubleshooting/office-shows-outdated-versions.md).

# Office affiche des versions obsolètes

## Situation

Lors de l'utilisation de Microsoft Office avec KONNEKT sur différentes plateformes, la dernière version peut ne pas apparaître dans des applications comme Word.

Un message peut également s'afficher : « Mise à jour recommandée : une version plus récente de ce fichier est disponible sur le serveur ».

## Problème

Il peut arriver que Word, Excel et PowerPoint affichent une version mise en cache du fichier au lieu de la version la plus récente de SharePoint Online (SPO).

## Solution

Il existe deux méthodes pour résoudre ces problèmes :

1. Effacez manuellement le cache Office à `%localappdata%\Microsoft\Office\16.0\OfficeFileCache`.
2. Activez « Supprimer les fichiers du cache de documents Office lorsqu'ils sont fermés » dans une application Office par utilisateur.

<figure><img src="https://2546298980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8zLVuKYctMIUr68_fs%2Fuploads%2FW5eer1S0svqtHvNDGX7m%2Fimage.png?alt=media&amp;token=0e5d571e-6e40-4f78-b70e-a9cb8a86953e" alt="Excel Options \ Save \ Cache Settings"><figcaption></figcaption></figure>


---

# 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://docs.konnekt.io/fr/troubleshooting/office-shows-outdated-versions.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.
