> 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/university/en/error-codes/gnx1205.md).

# GNX1205 – A Gonexa tag based on a main object is incorrect

Error code 1205 (GNX1205). A Gonexa tag based on the main object is in error in the merge fields when the document template is loaded.

**Error code:** `GNX1205`

## Error description

When the file is loaded into the Document template, a red cross appears and one or more tags (a tag being a character string that strictly starts with `{!` and ends with `}`) are in error in the Merged field tab.

## Solutions

### Tag in error

* Check that the label is exactly the same as the one defined in Salesforce
* Check the main object configuration
* Check the naming convention: the tag must start with `{!` and end with `}`
* Check that the API name exists
* Check that there are no spaces or symbols in the tag

### Empty result at generation even though the tag is identified in the merge fields

* If the tag is correct, check that the field in Salesforce actually contains data.


---

# 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/university/en/error-codes/gnx1205.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.