Scheduler moved occurrence to next day re-appear in Day view


#1

Hi,
I am updating the occurrence and move the occurrence to next day. It is creating a separate record in DB with parent event through the event_pid property. But the series is showing the same occurrence that I already moved in Day view.

e.g: Let say series starts from November 20, 2021 to December 01, 2021. The occurrence will occurs everyday.
I reschedule/move/drag the occurrence November 22, 2021 to November 25,2021. It is creating a separate record in DB with parent event through the event_pid property.
It is showing me again the November 22, 2021 occurrence in series Day view. However, I moved the November 22, 2021 to November 25, 2021.
At, November 25, 2021 it is showing me two occurrences one that moved from November 22, 2021 and second for November 25, 2021.

I greatly appreciate your help,
Thank you


#2

Hello @muhammmadahmed_ma ,

I tried to reproduce the described behavior in our samples, but the occurrence changes correctly:
https://recordit.co/ChjbwLH8VB

Could you please provide more details on how to reproduce the issue, maybe with screenshots or code fragments, or reproduce it in our snippet tool:
https://snippet.dhtmlx.com/5/7fcb44d90
(open the snippet => reproduce the issue on HTML/CODE tabs => click the “Share” button => send me a new link)

Please do not duplicate the same question in different places.


#3

Thank you for your response.
I think, the issue might be in scheduler.setLoadMode(“day”) mode. It is not showing the moved record in Month and week view as these views are getting the exception record.
As, the scheduler.setLoadMode(“day”) is fetching only the current day records and not fetching the exception record. How it will fetch the moved occurrence record exception to not show in day view?
Please find the issue video in link
https://drive.google.com/file/d/1fJzeFYVnFIyTwgPTyTWFtAe3vR2sPKnc/view?usp=sharing


#4

Hello @muhammmadahmed_ma,

Thank you for the video, and the description of the issue. I reproduced it and it’s a bug on our end, thank you for noticing it. I sent it to the dev team and they will work on a fix.

There is no ETA on a fix, but a possible solution is to change the backend:
https://docs.dhtmlx.com/scheduler/howtostart_nodejs.html#dynamicloading
in order to check out not only start/end dates, but also the event_length.

Or as a temporary solution, you can use the month load mode(that won’t fix the issue as it is, but will reduce it’s possibility).