The Data model provides a logical data architecture based on Table and Field items. The data mapping configuration is also based on these items.
A table is a container of data that depends on the application type. For EBX type applications, it is directly a table in EBX®. For XML type applications, it is a node in the XML file.
Property | Definition |
---|---|
Code | Any naming convention is valid. |
Application | Reference to the application that owns the table. |
Application type | Type of the application. |
Object Class | The table can be linked to an Object Class. This is the way to make an association between the logical data architecture and the business architecture. |
Name | Logical name of the table. |
Label | Label of the table. |
Path | The path of the table. |
Is removed | If set to True: The Table is no longer valid. It is logically removed. By using the purge service, data will be physically deleted If set to False: The Table is valid. |
Description | Description of the table. |
Index table | Determines the table's index position. During Excel export, this determines to which sheet number this table's data will be exported. |
A field is held by one Table only.
Property | Definition |
---|---|
Code | Any naming convention is valid. |
Table | Reference to the table that owns the field. |
Property | The field can be linked to a Property. This is the way to make an association between the logical data architecture and the business architecture. |
Name | Logical name of the field. |
Label | Label of the field. |
Data type | Reference to a Data type for the field. |
Parent field | Foreign key to a parent field in case the current field is a child node of another complex field. |
Order | Order of the field in table. The first position is '0'. |
Path | The path of the field. |
Is removed | If set to True: The Field is no longer valid. It is logically removed. By using the purge service, data will be physically deleted. If set to False: the Field is valid. |
Description | Description of the field. |