When modifying a detail entity (1-1 or 1-many), the parent entity is put into edit mode and flagged as 'modified' (ModifyParent call of the BaseDataSet). This is very handy for using TActions (e.g. Post & Cancel) linked to the parent entity but effectively posting/cancelling all data modifications (i.e. including all modified detail entities).
Unfortunately, this does not work for second detail level, i.e. master (A) -> detail (B) -> detail (C). Modifying detail (C) modifies the direct parent (B) but not the grandparent (A). In other words, the edit state does not travel up the hierarchy.
Is this by design (and remain as such) or is this something that will be extended in a future release? For reasons of writing efficient user interfaces, I think it would be a very useful feature.
Thanks, Mark