Skip to main content
Skip table of contents

DT416 Relation

Caution

  • If system customizing changes are made to data tables or data items (e.g. new data items created, data item parameters changed), the menu item Tools → Restart PLANTA service must be executed to make the changes visible.
    • Note: If you click on the menu item, all open client connections (sessions) are closed. New client connections are not possible during restart. Changes to I-texts, e.g. changes to the DI designation or adjustments to value ranges (including the VR type), present an exception.
    • Before restarting the service, the target directory must be deleted so that it can be created again when the service is restarted to ensure that the POJO classes it contains, which are responsible for the metadata of the data dictionary, are generated anew.

DI000277 Index

  • The index is the identification of the primary ID of a data table. Each data table belongs to exactly one index.
    • Example: Data table 461 Project: Index 461
  • The 1:1 relation of a DT is the basis for the name.
  • Example for naming indexes:
    • DT461 Project
    • Index: 461
    • Variable name: ID461

Note

  • All foreign key and primary key constraints on the database must also be stored in the Data Dictionary.

DI000278 ID of DI

Relations lead from an ident number in a data table to an index. This ID can be formed by one or more data items. Here, the first DI which forms part of the ID is entered.

Notes

  • For type = 2 relations: DI of the node ID.
  • The order is based on the DBPos from the data item.
  • Relations are only supported if they are of the same data type.
See also: ID to DI

DI000363 ID to DI

Last data item which forms part of the ID no. of the relation.

Notes

  • For type = 2 relations: DI to of the node ID.
  • Relations are only supported if they are of the same data type.
See also: ID of DI

DI000279 Relation

The quantity relation is specified from a data table up to the index:

Values

  • 1:1 = In the data table, an ID number equal to the index may appear only once
  • N:1 = In the data table, an ID number which is equal to this index may appear in an arbitrary number of records.

DI000951 Variable name

Contains the name of the ID in the database syntax

Examples

  • DT463 Task has a N:1 relation to DT461 Project.
    • The data item in data table 463 is called "ID461".
    • In the relation the variable name is = "ID461".
  • DT465 Link has two N:1 relations to DT463 Task.
    • As a result, there are two items in data table 465: "ID463A" and "ID463B".
    • The first relation has the variable name = "ID463A", the second has the variable name = "ID463B".

DI000281 Deletion flag

The deletion code describes the behavior for deleting records which are associated with records in other data tables.

  • In the data table which has the same ID no. as the index for the relation under consideration, one record will be deleted (referred to below as current record ). What happens to associated data records in the data table to which this relation belongs?

Values

  • 0: Deletion of the associated records without query.
  • 1: Query and possibly deletion of the associated records after positive confirmation by the user. If the user answers the query with No , the linked records will not be deleted and the current record will not be deleted either.
  • 2: The dependent records must not be deleted. I.e., the current record cannot be deleted itself.
  • 3: The relation is ignored when deleting. The current record is deleted in any case, even if it has dependent records via the relation in question.

Example

  • Data table = 461 Project
    • Relation: Index: = 463, Deletion flag = 2
  • Result:
    • If a project is to be deleted in DT461 Project , and there are corresponding tasks in DT463 Task , these tasks must not be included in the deletion. I.e., the project cannot be deleted itself.

Notes

  • Deletion flag = 3 may only be used for relations which do not have to be satisfied. Otherwise, data that is invalid from a user point of view may be generated.
  • Used mainly for relations between different databases when a deletion cannot or may not be performed in the other database at the same time.

DI000379 Create implicitly

Controls the behavior of the software if a higher-level data set required by the relation is not available.

Values

  • 0: If the parent record does not exist, an error message will be displayed.
  • 1: If the parent record does not exist, it will be created.
  • 2: Record is created implicitly, the error message is suppressed.
  • 3: The relation is ignored during creation and no dependent record is created if it does not exist.

DI001978 Recursion ID from

Recursion ID from. First data item which forms part of the ID of the successor node. Is only used for

Rel. type

= 2.

DI001979 Recursion ID to

Recursion ID up to last data item which forms part of the ID of the successor node. Is only used for

Rel. type

= 2.

DI000374 Relation type

Relation type

Values

  • 0: is considered a quantity relation by PLANTA
  • 1: remains unconsidered in the internal determination of module logic in PLANTA
  • 2: Recursion relation

Example

  • Unconsidered relation:
    • Task link: the second relation (to the predecessors) has Rel. type = 1
  • Recursion relation:
    • Module with at least 2 areas:
      • a node area (area 1): the data (records) in this area are to have a structured representation.
      • a linkage area (area 2): the data (records) in this area contain the structure information
    • Example
      • Area 1: Task; they are to be displayed as a node in the network
      • Area 2: Link: they show the successor of the parent task (node)
      • It must be possible to find the records in area 2 by means of a normal database relation.

Information in the Data Dictionary

  • The following is described in the data dictionary:
    • a) Path from a node to the linking object
    • b) Path from the linking object to the next or subordinate node
    • This is effected via 2 recursion relations.
  • These specify
    • for a) (in the first recursion relation):
    • for b) (in the second recursion relation):
      • 1: DI(s) which form the ID of the next or subordinate node ( Rec. ID from, Rec. ID tocolumn) error
      • 2: DI(s) which form this node ID (ID of the successor) in the linking object ( ID of DI, ID to DIcolumn) error
  • In the example,
    • a1: Task ID in the task
    • a2: Task predecessor ID in link
    • b1: Task ID in the task
    • b2: Task successor ID in link

Information in module area assignment

  • Res. parent area

Information in the area

  • DIs of class 8 for information on the required link type.
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close