DE EN EN (Google)

Data model

In the data model, the current data model Current can be viewed, and with proper access rights the development version Development can be viewed as well. Activate Changes to accept changes made in the development version. This will overwrite the current version.

NOTE: Be aware that this process causes a lot of activity on the server side, A complete re-indexing of all records. Until full indexing, users may find records in the old format. In some cases, it may also happen that records affected by changes are not displayed to users until the re-indexing is complete.

Definition of fields

Object types and masks are defined in the data model. Object types describe the structure of the data in the database. Masks describe the input and output views of the object types and therefore the data records. If, for example, 20 fields are defined for an object type, different field combinations can be viewable from masks. For instance, user 1 could have the right to mask 1, perhaps 5 of these fields. User 2 could be provided with mask 2, another 5 fields and with mask 3 they could view the other 15 fields.

NOTE: It is possible to hide individual fields for certain users or groups and to refine the view of an object type and its corresponding masks using the field rights for the object type.

Export/Import data model

easydb offers the possibility to download the data model of any easydb instance and to save or reuse it as a JSON-file or a CSV-file. A JSON file contains the configuration of all object types with associated masks and settings. A CSV file contains the tables for all object types without masks and without settings.

It is also possible to import an externally saved data model (JSON & CSV) into easydb.

The data model can be downloaded and uploaded via the data model in the main menu. It is available below the list of object types in the development environment via the cog-menu.

NOTE: The upload of a data model is intended for the transfer of existing data models into newly set up easydb 5 instances. Uploading to an instance with already existing data model is not possible.

Use cases

  1. The download and upload of data models makes it possible to transfer data models to other empty easydb’s. This is especially recommended in JSON format, since masks and settings for the object types are also saved.
  2. The download contains either the current data model or the development status, depending on which tab you are on when the download was started.
  3. The use of stored data models facilitates the rapid creation of new instances if they are supposed to base on existing data models.
  4. Holding ALT during download resets the current version number and starts at 1.
  5. Data models saved as CSV can be displayed in a table. CSV files can be opend with Spreadsheet Programs such as Excel. The tables for all object types are displayed in one spreadsheet.
  6. For example, a CSV can be used to add translations for the data model outside the database.
  7. With the backup of CSV files at regular intervals, the development of a data model can be documented.

Reset data model

The menu within development environment provides the option to reset the data model in development mode. Changes within the data model in development mode are thus reset to the status of the current data model.


The Objectstore (data model server) works as a node, which allows to work on a data model from different instances. The current data model is stored in a virtual environment and synchronized with other instances before further changes can be made.

If the Objectstore is configured, a -button appears next to the -menu.

Ist der Objectstore aktiv, kann über das -Menü mit Datenmodell auf dem Server überprüfen ein Check aller Datenmodellversionen durchgeführt werden. Es wird dabei verglichen, ob die Version, die im Objectstore ist, diesselbe ist, wie sie lokal installiert ist. Sollte es ein Problem geben (z.B. fehlende Version oder Mismatched), dann bietet das Frontend an die lokalen Version auf den Objectstore zu speichern (und damit alle Versionen im Objectstore zu überschreiben).

If the Objectstore is active, a check of all data model versions can be performed via the menu with Check Data Model on the Server. It is compared whether the version that is in the Objectstore is the same as it is installed locally. If there is a problem (e.g. missing version or mismatched), the frontend offers to store the local version on the Objectstore (and thus overwrite all versions in the Objectstore).

NOTE: Here you find instructions for the installation.

Graphic of individual data model

The options menu allows you to visualize the structure of the data model. The current data model can be downloaded as an svg graphic.

Graphic of the data model