The relation data form is used to manage all relations of the application. While the logical definition is done in the entity data form in connection with the related entities, the relation tables can be created in the database here. Additionally, links from and to relation tables can be created and managed.
Table Fields |
Link-1/Link-2 |
View | name of the relation |
Table | name of the relations database table |
Object Title | title of the object |
Refine List | name of the refine list for the relation |
Aggregate List | name of the aggregate list for the relation |
Comment | comment for the created relation record |
Create Table/View | creates the relation table in the database |
Delete Table/View | deletes the relation table in the database |
Create Ref List | creates the default refine list for the relation. |
Create Agg List | creates the default aggregate list for the relation |
Access to Relation | opens the relation access form |
attribute | master attribute for relation (T_ENT_REL) |
type, entry | string, entry required |
max. no. of characters | 20 |
selection tool | no |
multilingual field | no |
The View is the unique ID for the relation in the data model. You need it to identify a specific relation between two entities when there is more than one.
You can alter the View after the record has been saved, but not if the database table and the refine or aggregate list have already been created. In this case, you need to delete these objects first.
Table
After editing the relation record, you first need to create the table fields for the relation's attributes. Then you can physically create the table in the database.
Object Title
attribute
master attribute for relation (T_ENT_REL)
type, entry
string, entry optional
max. no. of characters
20
selection tool
no
multilingual field
yes
The title is used in error messages.
Note!
You should always give your objects a title. If you don't, error messages will only contain the object's key, and you won't be able to find the object in a Search mask.
Refine List
The default list can only be created when you already have a database table for the relation. The list contains the child entity's significant master attribute fields and the relation attribute fields. The default list record and its field assignment can then be found in the Mask Data form, and can be used as a template for other lists.
Note!
Once a default list has been created, it cannot be overwritten by creating it again. You first need to delete it from the Mask Data form. The Field Selection menu lists all the lists and forms which already exist.
Aggregate List
The default list can only be created when you already have a database table for the relation. The list contains the parent entity's significant master attribute fields and the relation attribute fields. The default list record and its field assignment can then be found in the Mask Data form, and can be used as a template for other lists.
Note!
Once a default list has been created, it cannot be overwritten by creating it again. You first need to delete it from the Mask Data form. The Field Selection menu displays all the lists and forms which already exist.
Comment
attribute
master attribute for relation (T_ENT_REL)
type, entry
string, entry optional
max. no. of characters
255
selection tool
no
multilingual field
no
Create Table/View
Before creating the relations table, you first need to create the table fields for relation attributes in the Table Fields sublist.
Attention! Do not use Create Table/View while the application is running. Always ensure that no other users are using the tables first.
DataView automatically checks to see if this table exists, and creates one if necessary. If it exists, DataView will adjust it, either directly in the database (for minor modifications) or by starting an Export/Import with the binary loader (for major modifications). Before starting the loader, it makes a security check.
If the loader is used, DataView automatically does the following (you can follow the process in the Messages Console):
If DataView is unable to create the new table because of definition errors, the loader file remains in the tmp folder. After correcting the definitions, the function can be called again.
Note! When altering (setting) the Non-Zero flag (to zero), ensure that there are entries for every possible user record in the modified table column. Otherwise DataView will be unable to load the loader file into the new table.
Note! DataView always uses the binary loader, even if the ASCII loader is selected in the LOADER default.
More information:
-> Deleting or modifying model objects
Delete Table/View
Attention! Do not use Delete Table/View while the application is running. Always ensure that no other users are using the tables first.
When a relation table is deleted, the repository retains all the entity's descriptive data.
More information:
-> Deleting or modifying model objects
Create Ref List
You can create the default list as soon as the relation has a master table.
The default list holds all significant master attributes of the child entity and all relation attribute fields. The default list record and its field assignment can be found in the Mask Data form, and can be used as a template for other lists.
Note!
Once a default list has been created, it cannot be overwritten by creating a new one. You first need to delete it from the Mask Data form.
Create Agg list
You can create the default list as soon as the relation has a master table.
The default list holds all significant master attributes of the parent entity and all relation attribute fields. The default list record and its field assignment can be found in the Mask Data form, and can be used as a template for other lists.
Once a default list has been created, it cannot be overwritten by creating a new one. You first need to delete it from the Mask Data form.
Relation Access (menu only)
This function extends the scope of the standard Access function. Access privileges apply not only to the relation object, but also to all lists and forms which refer to it (i.e. every mask which the application calls with userexits such as iwf_lis_ref, iwf_lis_agg,...). For example, users with access to the masks may only edit records in them if they have also been granted access to the relation object.
More information:
-> Access to records