Issue description
When a topic is displayed in the fact sheet or form of a counter player, it is sometimes necessary to reduce the number of fields that are relevant to the most important ones. This is currently possible for row adjuncts by defining a row view. It makes sense for sheet adjuncts as well.
Developer comments
Generalize the recently created association type.
The reason this whole issue surfaces now is deeper than previously described. Adjuncts are topics which need another topic to exist, its coadjunct, e.g. an invoice position is an adjunct to an invoice. If the invoice is deleted so is the position, it is necessarily dependent. As an invoice is movement data it is rarely referred to and only within a limited time period, so is the invoice postion. The whole story changes when adjunct and coadjunct are master data and frequently referred to/association rich. If you display such an adjunct as a sheet the fact sheet of the coadjunct will explode and be difficult to read. In such a case the adjunct/embed view comes to the rescue.
Use cases
An store has a topic type customer which have 1 to n loading locations. These loading location are used in orders, since you need to know where they pickup and delivered to. The loading location instances are adjunct to the customer instances, but should only display a fragment of the information available, in particular not the orders in the sheet, but in the fact sheet.
This was almost finished. Only needed to respect the embed view when the form is editing an coadjunct.
|
Work sessions2
| Start |
2025-12-22T14:42:08
|
| End |
2025-12-22T15:51:13
|
| Participant |
Robert Cerny
|
| Start |
2026-01-28T08:03:29
|
| End |
2026-01-28T08:51:52
|
| Participant |
Robert Cerny
|
|