> 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/gnx1206.md). # GNX1206 – A Gonexa tag based on a child object is not replaced at generation Error code 1206 (GNX1206). A Gonexa tag based on a child object is in error in the merge fields or is not replaced at generation. **Error code:** `GNX1206` ## Error description When the file is loaded into the Document template, one or more tags are in error in the merge fields tab *(Merged field)*, or the child object is not replaced. ## Solutions ### Tag in error * Check that the tag label is exactly the same as the one defined in Salesforce for the child object concerned * Check the child object configuration * Check the naming convention: the tag must start with `{!` and end with `}` * Check that the field API name exists on the child object ### Empty result at generation even though the tag is identified in the merge fields * Check that the child tag is placed inside a Word or Excel table * Make sure your Salesforce data contains records matching the filters on your child object * Enter the tag on the first row of the table only * You cannot use the same child object several times in the template ## Limitations * Data from several child objects cannot be combined in the same table * Child objects repeat by row, not by column * You cannot put child tags on several rows of the same table ## Workaround Create several child objects based on the same Salesforce object with different names, one for each table in the document. --- # 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/gnx1206.md?ask=&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.