> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/error-codes/gnx2207.md).

# GNX2207 – JSON avec des extensions de balises fausses

Code erreur 2207 (GNX2207). Erreur apparaissant à la génération lorsque des balises de champs texte enrichi utilisent des extensions non valides.

**Code erreur :** `GNX2207`

## Description de l'erreur

Lors de la génération du document, l'erreur apparait. Votre document contient une ou plusieurs balises avec des extensions non valides sur des champs de zone de texte enrichi.

Voici des exemples de balises avec des extensions incorrectes :

* `{!Account|Commentaires__c(HTML,f,c,e)}` : l'extension « e » n'existe pas
* `{!Account|Commentaires__c(HTML,a,p)}` : les extensions « a » et « p » n'existent pas

## Solutions

### Fournir le JSON au support

Cocher la case `gnx__Save_json_data_in_log__c` depuis l'onglet Document template en question afin d'enregistrer le JSON dans les logs. Puis, relancez une génération et récupérez l'information contenue dans le champs « JSON data send ». Copiez le et envoyez le au support Gonexa afin de pouvoir investiguer sur le sujet.

{% hint style="info" %}
Si une extension de balise est fausse, cela rien renvoie rien.
{% 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://university.gonexa.fr/error-codes/gnx2207.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.