relationtarget Table (51)
Some tooltip text!
• 2 minutes to read
• 2 minutes to read
Definition of targets for a relation. Links a relation definition (RelDef) to source and target tables. In general, a relation can be created between any pair of tables. This table is used for specifying which table pairs a particular relation can be used for. A relation definition should have at least one row in this table, and can have more. Note; The 5.0 Maintenance and GUI only support contact and person as valid values for the source_table and destination_table fields, in any combination. Other relations will not be shown, and relation definitions pointing to other tables will not be editable from the Maintenance GUI; however, nothing will crash.
|reldef_id||Reference to definition||FK relationdefinition|
|source_table||Source table number (contact/person in 5.0)||TableNumber|
|destination_table||Target table number (contact/person in 5.0)||TableNumber|
|bidirectional||Is relation bidirectional||UShort||●|
|registered_associate_id||Registered by whom||FK associate|
|updated||Last updated when||UtcDateTime|
|updated_associate_id||Last updated by whom||FK associate|
|updatedCount||Number of updates made to this record||UShort|
|associate||Employees, resources and other users - except for External persons|
|relationdefinition||Definition of a relation. This table defines the relations that can exist in the database. Each relation has an active text and a passive text. The table RelationTarget specifies which pairs of tables this relation can connect. Use of the active and passive texts is dependent on which direction the relation is viewed in, e.g., active text = "Owns" and passive text = "Is owned by".|
- Replicate changes DOWN from central to satellites and travellers.
- Replicate changes UP from satellites and travellers back to central.
- Copy to satellite and travel prototypes.
- No access control via user's Role.