I've been playing with the Scheduler using the Javascript web-variant of the control. I finally managed to get it to properly send UPDATE, CREATE, and DESTROY requests to my MVC4 controller. I also captured some of the traffic from the online demo to see what the proper JSON responses were for those requests from the controller.
My question, though, is how do I reject a delete request, for instance, if the backend code and database (MySql in this case) cannot process and manage the request, for instance? I haven't found any documentation (yet) that suggestions how to stop the scheduler from going ahead and removing the item from the control anyway, regardless of the response (it also removes right now even though my controller returns a "not implemented" server message).
My question, though, is how do I reject a delete request, for instance, if the backend code and database (MySql in this case) cannot process and manage the request, for instance? I haven't found any documentation (yet) that suggestions how to stop the scheduler from going ahead and removing the item from the control anyway, regardless of the response (it also removes right now even though my controller returns a "not implemented" server message).