Configuring the data model
Information associated with a data model
To view and edit the owner and documentation of your data model, select 'Information' from the data model 'Actions' menu for your data model in the navigation pane.
Note
This area is available only to authorized users in the 'Advanced perspective'.
Unique name | The unique name of the data model. This name cannot be modified once the data model has been created. |
Owner | Specifies the data model owner, who will have permission to edit the data model's information and define its permissions. |
Localized documentation | Localized labels and descriptions for the data model. |
Permissions
To define the user permissions on your data model, select 'Permissions' from the data model 'Actions' menu for your data model in the navigation pane.
The configuration of the permissions of a data model are identical to the options for the permissions of a dataset, as explained in Permissions.
Data model properties
In the navigation pane, under Configuration > Data model properties, you can access the following technical properties:
Dataset inheritance | Specifies whether dataset inheritance is enabled for this data model. Dataset inheritance is disabled by default. See Dataset inheritance for more information. |
Disable auto-increment checks | Specifies whether to disable if the check of an auto-incremented field value in associated datasets regarding to the "max value" found in the table being updated. |
Included data models
You can use data types in the current model that are defined in another data model by adding an entry for the other data model in the table under Configuration > Included data models.
When you access the record of an included model in this table, you will find technical information about the model under the Information tab. As an included data model could eventually have validation errors, for example, due to deleted Java resources, this view will provide information regarding those issues.
It is only possible to include data models that have no validation errors and have been defined and published as an embedded data model or packaged in a module.
The names of data types must be unique across both locally defined and included type definitions. That is, included data types must not have names that coincide with those of data types defined in the current data model or other included data models.
User guide table of contents