BuyLog In
Bug Report T283357
Visible to All Users

Web - Aggregated detail collection changes are not saved when the CollectionsEditMode = View setting is adjusted for the master DetailView

created 10 years ago

Hello,

I set this setting in model:

XML
<DetailView Id="Phone_DetailView" CollectionsEditMode="View" />

I do not know how to save changes in this mode when I edit a collection in View mode.

Sign in to comment on this post

Answers approved by DevExpress Support

created 9 years ago

We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

    Sign in to comment on this post
    created 9 years ago

    Hello Pawel,
    In the earlier versions of XAF, there was no capability to open a new DetailView in Edit mode from the nested ListView when the master DetailView was opened in View mode.
    Starting with v15.1.9 and 15.2, for this scenario, the new object for the opened DetailView is always created in the root ObjectSpace with the link to the parent object. After committing this DetailView, all changes are saved to the database.
    Let me know if you need any further assistance.

      Comments (2)
      PB PB
      Pawel Botwina 9 years ago

        Hello,
        Creation and deletion work in 15.2.3 but update is not committed.

        AG AG
        Alex Gn (DevExpress) 9 years ago

          Hello Pawel,
          Thank you for your comment. We have now supported the editing functionality as well. This functionality will be available in the next update. Currently, you can request a hotfix to get an intermediate build with this functionality.

          Sign in to comment on this post
          created 10 years ago (modified 10 years ago)

          Hello Pawel,

          I can replicate this behavior and it is caused by an issue in our code, which is related to this model setting: Web - DetailView CollectionsEditMode=Edit does not work as we expected. We have already fixed it for the next version and you are free to request a hotfix. Alternatively, if you set the global setting at the XafApplication level, everything will also operate as expected.

            Show previous comments (2)
            Dennis Garavsky (DevExpress) 9 years ago

              Pawel,

              Would you please clarify the desired result in greater detail? In particular, do you ultimately want to have only one DetailView (Phone_DetailView) operating with CollectionsEditMode=View? Can you additionally configure the same setting for the nested record object DetailView (Number_DetailView)?

              PB PB
              Pawel Botwina 9 years ago

                I have one Configuration class (in my production application) with dozen nested listviews. I just want to make CRUD operations on these lists without clicking save (or save and close) action for the whole Configuration's DetailView. I thought the CollectionsEditMode = View would do the trick but it does not commit changes.
                Configuring the same setting for every nested DeailView is not an option. I think the single setting for the parent DetailView should be enough. Setting the same option for every nested detailView is strange to me and not intuitive at all.
                Even the setting's name is: CollectionsEditMode so One can assume it should affects every collection on the DetailView.

                Dennis Garavsky (DevExpress) 9 years ago

                  Thank you for your confirmation and describing your real situation, Pawel. We will update this thread once we have any news.

                  Sign in to comment on this post

                  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.