/ doc / toc / ARCQuery / Class / ForeignKey / IPRelationsKeysPointingTo / __TOCDet / Attribute / LongDescription

LongDescription

Edit keys at this level only

= Example:0x000D0x000A0x000D0x000AIf we have classes Customer, Order and SupportTicket and property keys OrderP.CustomerId and SupportTicketP.CustomerId then the entry for the key 'Customer' would be like   new List0x003CEntityTypeAndKey0x003E 0x007B "Order CustomerId", 'SupportTicket CustomerId' 0x007D.0x000D0x000A0x000D0x000AThis may be used to dynamically and automatically create links to related objects. For instance for context   'Customer/42' it will (with the help of this information) be possible to create corresponding links   'Order/WHERE CustomerId = 42' and   'SupportTicket/WHERE CustomerId = 42'.0x000D0x000A0x000D0x000ARelations defined with -PKRelAttribute- (-ForeignEntity-) is also taken into account.0x000D0x000AFor instance for Employee there might be a key EmployeeP.SupervisorId pointing to another Employee.0x000D0x000ATODO: Document use of -OppositeTerm- in such cases.0x000D0x000A0x000D0x000ANote that as of Jun 2020 this concept relies on predefined property keys (-PropertyKeyEnum-).0x000D0x000AThere is however in principle nothing wrong with dynamically finding the same information, as long as 'standardized' names are used for foreign keys, like 'Order/1968/CustomerId = Customer/42' for instance.0x000D0x000ATODO: Consider implementation of such a dynamic discovery.

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Generated 2024-05-17 22:23:16.292 UTC