Our powerful JS Calendar component


Post by lx0 »

Hi,

I encountered an issue with the reassignment of one event of a series to another resource when using the CrudManager in Calendar 6.0.2.

When changing the assigned resource of a recurring event and selecting the "only this event" option in the dialog, the CrudManager sends unexpected operations. Typically, when selecting "only this event" I expect an "update" operation which excludes the changed event date from the original series and an "add" event which creates a new event with the newly assigned resource. This also works as expected but only for the first event of a series. When changing the resource of the second event of the series, only one "update" Crud operation is being sent.

This unexpected behavior only happens when changing an event within a series (not the first event) and only when changing ONLY the assigned resource via drag-and-drop. When changing the startDate along with the assigned resource, the Crud operations are generated as expected.

Attached you will find a working example. Please start the frontend and backend, reassign the event "Hackathon 2020" on the 21.10.2020 to another resource (keeping the same date/time) and select "only this event" and watch the network tab.

BR,
Alex

Attachments
Expected behavior: Changing resource and startDate triggers "update" and "add" operation.
Expected behavior: Changing resource and startDate triggers "update" and "add" operation.
Screenshot 2024-07-30 at 12.04.39.png (67.48 KiB) Viewed 252 times
Unexpected behavior: Expected behavior: Changing only resource triggers only "update"  operation - and this is even wrong.
Unexpected behavior: Expected behavior: Changing only resource triggers only "update" operation - and this is even wrong.
Screenshot 2024-07-30 at 12.03.06.png (12 KiB) Viewed 252 times
calendar-angular-basic-crud-change-resource.zip
(173.77 KiB) Downloaded 18 times

Post by helgetan »

The Bug is blocking us from upgrading to 6.X


Post by tasnim »

Hi,

I'm not able to run your application, when I did npm start it is showing this error

Screenshot 2024-07-30 213903.png
Screenshot 2024-07-30 213903.png (148.79 KiB) Viewed 226 times

What are the steps we'd need to follow to run your application?
Could you please provide an error free test case where we can reproduce your issue easily so we can debug it?

Best regards,
Tasnim


Post by Animal »

Looking at the changes that the CrudManager calculates, it all looks right:

Screenshot 2024-07-30 at 18.20.29.png
Screenshot 2024-07-30 at 18.20.29.png (738.39 KiB) Viewed 221 times

I changed "Get Firewood" to occur daily. Then I changed the assignments of the one on the 30th and the 31st

You can see that the change set has two added assignments where I assigned those.

There are two newly added events which are the new exceptions on those dates

And the base event has two exceptionDates for the two I changed (In addition to being set to recurring)


Post by lx0 »

tasnim wrote: Tue Jul 30, 2024 5:40 pm

What are the steps we'd need to follow to run your application?
Could you please provide an error free test case where we can reproduce your issue easily so we can debug it?

The frontend is basically the Bryntum Angular Basic example with just minor changes. These changes do not affect the application architecture or how it is installed and started. So please run npm i && npm run start and it should work.
You will have to start the backend as well via npm i && npm run dev.

The test case to reproduce the issue I've mentioned in my initial post:

reassign the event "Hackathon 2020" on the 21.10.2020 to another resource (keeping the same date/time) and select "only this event" and watch the network tab.


Post by ghulam.ghous »

Hi there,

Thanks for the report, I was able to reproduce the behaviour mentioned by you and created a ticket here to investigate this issue: https://github.com/bryntum/support/issues/9726

Regards,
Ghous


Post Reply