In Application.CollectionsEditMode=Edit mode everything works as expected, for example after calling save&close on child object's detail view nothing is written on database until parent object's save action is called. that's perfect and what we need.
We decided to use Application.CollectionsEditMode=View mode for Collections in all detail views, except needed ones.
But when we switch to Application.CollectionsEditMode=View and set DetailView.CollectionsEditMode=Edit on required detail views, this does not work like Application.CollectionsEditMode=Edit.
Creating new child or editing child and then saving&closing child object saves the parent object also and returns to the parent's detailview.
Hello Destek.
Thank you for your report. We need additional time to research this issue. We will get back once a solution is found.
Parent's detailview switches to view mode too, maybe that causes this behaviour.
Hello Sukru,
I have reproduced the described problem. The behavior looks like a bug. I have forwarded this ticket to our developers for further research. We will do our best to resolve the problem as soon as possible. Please add this thread to your Favorites to be automatically notified of our progress.
Hi Aleks,
I have the same problem. Can you give me a prevision to solve this or any other alternative way?
@Gilson: Thanks for your feedback. We have not yet found a good solution for this. We are researching possible options (they imply overriding the CanUseNestedObjectSpace and GetObjectSpaceToShowDetailViewFrom methods of the ShowViewStrategy and XafApplication classes) and will update this thread once we have any news.
Hi,
Application Level 'Edit' mode: child modifications are done in popup windows.
Application Level 'View' mode, and specific detail views in 'Edit' mode: child modifications redirect to new page not popup.
We expect the same behaviour when we set CollectionsEditMode to Edit in specific detailviews when it was in edit mode in application level.