Ticket S34378
Visible to All Users

Layout.Web - provide the capability to manage the display of detail collections, not on the global application level but, for each DetailView separately

created 15 years ago

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.

Comments (2)
Dennis Garavsky (DevExpress) 12 years ago

    I would be very grateful if you leave a comment here and answer the following questions about this feature request:

    1. How often did you require to display collections in the edit mode for certain detail forms only, while having them hidden in other forms by default? When did you meet this requirement last time?
    2. What you are currently using to fulfill this requirement?
      I would be very grateful if you leave a comment here and answer the following questions about this feature request:
    3. If you already have a solution, what are its implications in terms of cost, time and resources?
      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.

      Answers approved by DevExpress Support

      created 12 years ago (modified 12 years ago)

      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.

      Additional information:

      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; }
        Comments (1)

          This is fabulous, thank you.

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.