►NOTE◄ For changing/creating custom type definitions, a rudimentary knowledge of relational databases is necessary.

Training on the subject is recommended.

After saving a type definition, the changes are determined. These must be confirmed by the user.
Afterwards the changes are carried out in the database! Since columns may be added or removed, it should be ensured that no user is working with this object at this time (also no import).
Therefore it is recommended to carry out changes only in maintenance mode!
Furthermore, several users should not make changes to their custom type definitions at the same time!

With custom type definitions, a complete set of custom data structures can be created.

A basic distinction is made between two types:

Custom entity

Custom entities represent an independent entity, which gets its own rights and menu.

Two new database tables (Data + History) with corresponding names and their configured columns are created for each custom entity.

Custom attributes

Custom attributes are primarily considered as templates. They must then be implemented for an attribute owner. Only then are the corresponding tables and templates created.

Custom attributes did not support all field types (e.g. Repeatable entity).

Cyclic definitions

Cycles can be defined conditionally. These can arise very quickly e.g. with custom attributes. These are structurally allowed, but no cycles are allowed in the data. e.g. Shipment1 → CustomAttribute → Shipment1 is not allowed, whereas Shipment1 → CustomAttribute → Shipment2 is allowed.

Cyclic references to the same entity is possible only if the 'reference only' option is enabled.