Data Types for Object Type Fields

yuuvis® RAD designer 9.x

Create fields for metadata for each object type. A column with the corresponding data type is created for each field in the database table of an object type.

Fields are created and added with the technical name, display name, and data type via the header of the Fields view area.

Data type	Usage
Boolean	Describes three states: true / false / neutral
Date	Date values
DateTime	Date and time values accurate to within a second. The date must be between 01/01/1753 and 12/31/9999. The data type 'Date' is not restricted. In yuuvis® RAD client, only hours and minutes are entered and displayed for the time.
DateTimeEx	Date and time values accurate to within a millisecond. In yuuvis® RAD client, only hours and minutes are entered and displayed for the time. Various search options such as the interpolation search are not available in fields of this type. Therefore, this data type should be only used if fields of this type must not be searched.
Decimal	Decimal numbers with a maximum of 36 digits, regardless of the position of the decimal point.
Integer	Integers of -2³¹ to 2³¹-1. Entries that fall outside this range will cause rounding or other errors.
Long	Integers of -2⁶³ to 2⁶³-1. Counters can be assigned to fields of this type via the Default property. It is technically possible to process numbers outside the integer range, but they cannot be entered or displayed in yuuvis® RAD client without errors.
ID	System-wide unique IDs. With classification: Organization object reference for users and groups Business object reference for object types. ID fields without classification are used in the sense of technical fields. Generally, users in yuuvis® RAD client should not edit them. ID fields without classification are not integrated in form templates that are generated by the system. However, they can be integrated in defined form templates and used for administrative purposes.
CatalogEntry	Fields of this type can be linked to a catalog. Users can then enter a value from the linked catalog into the corresponding form field. Groups of radio buttons for options are also created via catalogs.
String	Strings of various lengths, depending on the database up to 4,000 characters.
StringEx	Strings that are too long for the 'string' data type.
Table	A table consists of a number of columns, TableColumns, which are created via the context menu and are assigned properties analogous to fields. The alignment of the content can be specified on forms. Tables with more than 20,000 rows lead to errors when reindexing. Reindexing may also be necessary for Elasticsearch updates. If columns of type String in multi-column tables are assigned the Field reference and Autocomplete indexing properties, this may cause significant performance problems. All or individual columns of a table can be integrated in a form.
Set [String] Set [StringEx] Set [CatalogEntry] Set [ID]	Multi-field for entering multiple values.

If a date is entered in a date field, then the local date is not saved in the database; the time in GMT is stored there. The relevant local time is shown in yuuvis® RAD client based on the saved GMT time. This could result in a one-day difference between two time zones, particularly along the date line.