CRUD Create and Update Firing Twice

Hello Cyndie,

Unfortunately, the provided details are not sufficient in order to track the exact cause for the issue in question. However, I suspect that it may be due to incorrect format of response from the server. Could you please verify that the response structure match the one defined in the Scheduler's schema definition. 

If you continue to experience difficulties please provide bit more details about the exact structure of the response, the scheduler declaration etc.

Regards,
Rosen
Telerik

Is the expected response for Create and Update different than for Read?  

Read only fires once, so it seems to like that response format.  I'm using the same Class in my web service for Read, Create and Update.  The only difference I see is that Read returns a List<Event> and Create and Update are just returning a single Event.  I tried changing Create to return a List<Event> like Read, but it still fires twice.

I also tried to change my Create Event to read the event back from the database identically to Read and return that instead of returning the event passed to it with no luck.

Hello Cyndie,

Indeed, the structure of the response should be the same for all of the DataSource CRUD operations.
Please provide a small runnable sample in which this behavior can be observed locally. This way we will be able to gather more details about the implementation and configuration of  your scenario and provide you with more to-the-point answer.

Regards,
Rosen
Telerik

Unfortunately, I'm not sure that there is an easy way to create a runnable sample from this.  It is an intranet site, so you won't be able to query my web service.  This is why I originally wondered where in the code it is checking the response to put a break point, so I can step through it and try to figure out what is failing. 

I thought it might be related to the multi select that I have in my editor template, but I commented it out and still have the problem.

I figured the problem out.  I have an editor inside my event template and if I changed something only in the editor, I had to manually mark the record in the datasource as dirty, and had a call to sync there that I didn't need.