How can we help?

Search for answers or browse our knowledge base

< All Topics


The Header of a component is its most important attribute.


  • The Header defines the name of the database table/view field with which the component will exchange information unless the component is part of a transposition.
  • The Header of a component is a unique identifier within the containing branches: root/pattern or root/multi-tab or root/multi-tab/pattern

Uniqueness of headers

Two components can have the same Header if, for example :

  • they are in two different patterns
  • they are in two different multi-tabs
  • they are respectively in an independent pattern and multi-tab, the pattern not being in the multi-tab

Two components cannot have the same Header when, for example

  • one is part of the root
  • one is part of the multi-tab (outside the pattern) and the other is in a pattern of the same multi-tab

The uniqueness of headers is checked during an Excel import into Design. The uniqueness is checked after the import and a dialog box warns you of the presence of duplicates and prompts you to view them for correction. If you refuse, it will not be possible to save the document.

  • You can use the Tools Check Header Uniqueness function at any time


  • Headers are case-sensitive. For example, Edit and EDIT are two different headers.
  • A header cannot contain control characters (ASCII code < 32) or any of the following characters: , ; ! ? ” ` ^ ¨ ~ ° ¤ [ ] { } |

Use of the Header in Design

The Header is used to designate the source of a drop-down list or the source for item selection when adding a tab in GTAnswer.

Exposing a clear label to users

The Header will be exposed to users when attempting to transmit a response for a form with at least one mandatory component not filled in.
However, the Header is often not very “meaningful” for a functional user, either because it uses the database naming convention or because it is very long (this is particularly the case for components included in a transposition).
In this case, it is advisable to use the “Display name” property of the component, making it possible to assign a functionally explicit label to a component.

Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Previous Statement Date
Table of Contents