Attributes of Relationship Types
Definition
Refining a relationship type.
Use
Attributes are optional: Therefore if you want to describe a relationship in a more detailed way than just by its type, you must assign one or several attributes to the relationship type in the model.
Structure
You must define persistent attributes, like relationship types, in a special application table. The attributes are transferred as character strings of length 250. They are split via a structure into single fields, which you define as the Attribute Format in the relationship model. You can define a structure with a single field if you only want to transfer a single attribute. When writing a relationship you can transfer a whole table of attributes with the API ( Data type T). For example, you can therefore transfer several fields with the attribute Filter, which were filtered accordingly.
The application tables must have the following structure:
|
Field |
Key |
Field Type |
Meaning/Use |
|
CLIENT |
x |
CLIENT |
|
|
RELATIONID |
x |
BINRELID |
Unique relationship number (GUID) |
|
POSNO |
x |
POSNO |
For attribute tables ( Data type T): Number of line in the table For one-line attributes ( Data type S) you must leave the field empty |
|
BRELTYP |
BINRELTYP |
Relationship type |
|
|
ATTRIBUT |
RELATTRIB |
||
|
.INCLUDE |
<your attribute format> |
Your structure is at most 250 bytes long |
At present, attributes can only be written by the API. Therefore, if you want to display your attributes, for example, in a separate browser, then you must write a function module which reads the attributes from the table and displays them correspondingly.