Currently, as a workaround, you need to implement descendants of the WebLayoutManager and WebDetailViewController classes as shown in the attached sample.
See Also:
How to: Display Collection Properties in an Edit Mode Detail View for an ASP.NET Web application
Layout.Web - provide the capability to edit an object when it's opened by clicking on a grid row in a nested ListView (ShowViewStrategy.CollectionsEditMode = ViewEditMode.Edit)
Thanks,
Dennis
Proposed Solution:
I think that we should introduce a new CollectionsEditMode attribute into the DetailView's schema for Web applications.
Layout.Web - provide the capability to manage the display of detail collections, not on the global application level but, for each DetailView separately
Answers approved by DevExpress Support
We have implemented the functionality described in this ticket. It will be included in our next update(s).
Please check back and leave a comment to this response to let us know whether or not this solution addresses your concerns.
Starting with the version 13.2, you will be able to control this behavior vis-a-vis the DetailView via the CollectionsEditMode property exposed in the Model Editor for Web projects:
XML<Views>
<DetailView Id="Contact_DetailView" CollectionsEditMode="View"></DetailView>
</Views>
The above setting in the XAFML file will enable the View mode only for the Contact DetailView, while the rest application will use the default mode or the one specified in code:
C#protected override void OnLoggedOn(LogonEventArgs args) {
base.OnLoggedOn(args);
((ShowViewStrategy)base.ShowViewStrategy).CollectionsEditMode = DevExpress.ExpressApp.Editors.ViewEditMode.Edit;
}
- v13.2.5Download Official Update
I would be very grateful if you leave a comment here and answer the following questions about this feature request:
I would be very grateful if you leave a comment here and answer the following questions about this feature request:
Thank you in advance!
often… I hit this with every app of late…
Currently managing client expectation as a work-around.
One thing that is critical is to have all the actions buttons working consistently regardless of view strategy. Collections having delete buttons for example should always show them even if the parent is in edit mode… This confuses clients when they disappear.