Bug Report T923353
Visible to All Users

QueryStart and QueryEnd use incorrect values in changed and deleted occurrences

created 5 years ago

Hi Team,

I have created a Recurring Schedule and edited one occurrence. The Query start and Query End date of changed occurrence showing the occurrence start and end date(as shown in the attachment). Is this is the expected behavior?

Thanks,
Litty

Show previous comments (1)

    Thank you

    Andrey Marten (DevExpress Support) 5 years ago

      Hi again, Litty.

      Our team discussed the current operation of the QueryStart and QueryEnd properties in changed and deleted occurrences and found scenarios where it can lead to incorrect results when data is retrieved from the database for a certain interval. We will additionally research these scenarios and will update this thread as soon as we consider changes that will enhance operation of these properties. You will receive corresponding notifications of our updates.

      May I mark this thread public so that other customers can find this thread?

      Thanks,
      Andrey

        sure…Thanks for the update.

        Answers approved by DevExpress Support

        created 4 years ago

        We have addressed the issue described in this ticket and will include a fix in our next maintenance update. To apply this solution before official release, request a hotfix by clicking the appropriate version link.

        Note: Hotfixes may be unavailable for betas/updates set for release within a week.

        Additional information:

        In previous versions, QueryStart and QueryEnd in modified and deleted occurrences were different from the QueryStart and QueryEnd values from the recurrence pattern. In certain scenarios, this can lead to incorrect load for such occurrences. For example, in a scenario where data was requested only for the pattern's QueryStart and QueryEnd interval, those modified and deleted occurrences that were declared outside this interval were not loaded from the source.

        In v20.2 and newer, QueryStart and QueryEnd in modified and deleted occurrences are always equal to the QueryStart and QueryEnd dates of the pattern.


          Comments (3)

            Thanks for the update.

            Currently we are in 20.1.6 and planning to go to 20.1.7 next week. So when can we expect the fix in 20.1 ?

            Thanks,
            Litty

            Andrey Marten (DevExpress Support) 4 years ago

              Hello Litty,

              We will introduce these changes only for the next major release - v20.2. In this upcoming release, we supported the FetchAppointments event and these changes in the QueryStart/QueryEnd properties are required to allow our customers to correctly process this event.

              We do not have such an event in v20.1 and this is why we did not add these changes in this version. If you observe certain issues related to the old operation of the QueryStart/QueryEnd properties in v20.1, please describe these issues in greater detail and share related code files. This will help us check if there is a solution for v20.1.

              Thanks,
              Andrey

                Thank you for the clarification.

                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.