Trigger Master save when Detail is saved

[L30P1N0]

Would there be a way to, when saving a Detail, trigger the save of the Master as well?

[asilmertkan]

Short answer: No, not in the way you’re describing — and it’s by design.

In Serenity, Detail records are not persisted independently.
They are kept client-side (in memory) and are only sent to the server
as part of the Master save request.

Key points

• In a Master/Detail setup, only the Master has a Save endpoint
• Details are serialized and posted together with the Master
• There is no standalone “save detail” operation that could trigger a master save
• Because of this, a “save detail → auto-save master” flow does not exist in the standard Serenity architecture

This design ensures:

• Transactional consistency
• No partial writes
• Clear ownership of persistence logic

If someone needs:

• Independent detail persistence
• Auto-saving on row edits
• Or cross-entity save orchestration

then that’s no longer a Master/Detail scenario — it should be modeled as
separate entities with their own services, possibly coordinated explicitly on the backend.

In short:
You can’t trigger a master save by saving a detail, because details aren’t saved at all — the master is.

If your use case requires saving details independently, it usually indicates
that Master/Detail is not the right modeling choice.