The entity as the central model object has several functions in DataView. On the one hand you use the entity to manage user data with the same characteristics in a master table, on the other hand you can use the entity to create -> views in the database, in order to set up task-specific user views on user data in tables. Additionally, entities can be used to integrate -> foreign tables into the data model or to provide a logical -> zero- entity.
In contrast to other model objects, the entity can be mapped in the database both as a table (master table) or as a view, respectively. Both database objects can use the DataView format or a foreign format. The setting is done in the field Type.
Entry | Comment | Confer |
T | Mapped as DataView table | -> Table Formats |
F | Mapped as foreign format table | |
V | Mapped as DataView view | -> View Formats |
W | Mapped as foreign view |
If the mapping is done using the -> DataView Format both the table and the view contain DataView-internal system fields in addition to the application-specific attribute fields. DataView automatically assigns an internal C_ID for unique identification to each record which will be subsequently entered in the table.
For the representation on the desktop you can first create a default list or a default form. Both masks display the fields contained in the master table or in the view and provide the standard functionality required to enter new records, to search, to modify, to display dependent data, etc.
Example: In the meditronic application an Item entity has been created to manage all items. The master attributes number, identifier and price are used as common features. The master table was created using the DataView format in the database. On the desktop a default list and a default form are used as first masks to input test data.
Please observe the following comments when you enter the database-relevant field attributes. If you want to create a view, the Table Fields sub-list will display fields attributes different from the ones described here. Further information can be found in -> view fields.
The following field attributes are optional. The details are important if the fields are used in masks. They are evaluated when the default master masks are created. You can overwrite these attributes when you refine the mask design later:
After saving the data for the entity object are stored in the repository. All created master table fields can be viewed in the Field Data form.
After that the master table or the view will exist in the database.
After that the data of the default master masks are stored in the repository and copied into main memory. The default masks and their corresponding mask-field relations can be viewed in the Mask Data form.
Note! You can immediately open a created default master list via the Manager menu (-> Open -> Application -> Select list) and enter test data. Thus you check that the object and the master attribute fields have been correctly created.