The manual states:
Choosing @Composition annotation as the relationship type enables making use of a special commit mode for datasources in edit screens. In this mode, the changes to related instances are only stored when the master entity is committed.
How can I still use composition (because the entity should only exists as a part of the owning entity) but save each sub-entity (e.g. airport terminals) as it is edited / created?
I want to avoid a situation where the user adds and edits a lot of sub-entities and then is at risk of losing a lot of work if they fail to save the main entity.
There is also a calculated field on the main entity screen based on the sub-entities. It is a transient meta-property in the main entity. When I do a refresh on the main entity datasource, it doesn’t refresh this calculation. How do I trigger this recalculation on the field in the fieldgroup?