We do have a Kendo Scheduler bound to a remote data source.
The transport configuration of this scheduler's data source is done using remote urls (for CRUD), and this works perfectly,
On the server side, we make a lot of checks. So if some requirements are missing, Create, Update or event Destroy operations wouldn't pass and user will be shown the meaningful error.
The problem we're facing now is like the following :
For the Destroy action, what kind of response should we send back (from the server) to the scheduler component (in the browser on the client side ) to prevent removal of events in the UI?
We've tried :
- Sending back HTTP 500 status code
- Putting an error field in the response and linking it to the schema.error configuration
But events are still removed from the UI, nevertheless the error event is fired. We even use this event to notify errors to end used.