Events issues if not refreshing the scheduler

[Julien]

Hello,

I have some issues with the scheduler:

- I create an event and go back to his edit form right after, if I click on Cancel the event disapears. If I refresh the scheduler the event is still there and I can cancel the event i won't disapear .

I  saw the same problem in another ticket (http://www.telerik.com/forums/events-disappear-after-canceling-the-detail-modal---help) but my event has an ID when I controll it in DEGUB.

- I have the same issue when I create an event and modify it right after. The event will be duplicated. But if I refresh the sheduler after the creation, I can modify it and it won't be duplicated.

 

I think both issues are linked. Do you have a solution ?

Thank you,

[Julien]

Let me update the issue.

After testing a lot, I observe that the first time a create an Event, it will have his ID but when I modify it without refreshing I will go again in my create controller and the ID of my Event will be 0.

[Ivan Danchev]

Hello Julien,

You mention refreshing the Scheduler, could you elaborate more on how you are refreshing it and which handler you are doing it in? Listing step-by-step the user actions that lead to the described behavior would also help us in reproducing it. As you can see in our live demos creating an event, then opening its editor (by double clicking the event) and then hitting Cancel does not make the event disappear.
In order for us to get an idea of your Scheduler configuration could you also post its declaration?

Regards,
Ivan Danchev
Telerik by Progress

[Julien]

I refresh the page manuelly by F5.

1 - User creats an event

2 - He modifies it and saves modification

3 - User refreshes the page and the event will be duplicated

But if I do those steps ther is no duplication:

1 - User creats an event
2 - User refresh the page.
3 -  User modifies the event and save modification. The Event will not be duplicated.

I provide you in attachements : my view, controllers, Event model and event repository. let me know if it's enough to analyze the issue.

Thank you very much for your time and effort.

 

[Ivan Danchev]

Hello Julien,

We checked the Scheduler's configuration and did not manage to find anything wrong with it. There are two missing event handlers (scheduler_save and scheduler_remove) that presumably contain logic related to the corresponding performed operation (could be related to the issue as well) and in that regard instead of using a common handler (scheduler_save) for the save and change events we would recommend using different handlers.
The model contains the necessary fields, which leaves the server logic responsible for the CRUD operations as potential source for the unexpected behavior. Debugging your Read, Create, Update controller actions and the corresponding methods in the repository could help you check whether they are called as expected and whether they return the expected data. We can also suggest comparing your specific server side implementation to the one we use in our Scheduler demos. We have a sample application included in the MVC suite installation that allows the demos to be run locally and their implementation to be inspected more closely. More details on where it can be found and how to run it you can find in our documentation.
You could also find this and the other Scheduler examples in our public Github repo helpful. It implements a similar service responsible for the CRUD on the Scheduler and it also works as expected without duplicating events on page refresh.

Regards,
Ivan Danchev
Telerik by Progress

[Julien]

I finally found the issue.

I removed ModelState.IsValid from my Create controller because it was always false. But the issue appeared because off this ModelState false.
So I manage to delete the attribut that caused me the ModelState false and everything is working great by now.

Thank you for your support.

[Jeffrey]

I had the exact same issue, and by adding the ModelState.IsValid check in Create in my controller fixed the dupelication of events.