Hi, I wanted to check the default behaviour on commit of nestedDatasources.
I am using nestedDatasource for associations (not compositions) in an Edit Screen. (The reason I do this is because properties of the nestedDatasource linking to the masterDatasource will be populated automatically when creating new instance).
When I create a NEW entity instance in the nestedDatasource, it is commited as soon created (i.e. even if I don’t click save in the Edit Screen).
However, if I EDIT or REMOVE an entity instance in the nestedDatasource, it is only commited if I click Save in the masterDatasource Edit Screen.
I thought that when NestedDatasources where ASSOCIATIONS, all changes would be commited as soon as the NestedDatasource entity is edited/removed. Is this behaviour correct?