DataSource sync() order of execution for CRUD operations

[Alexander]

I noticed that datasource sync() method always executes synchronization operations in the following order: Create, Update, Destroy.
It may cause a problem in some cases. Consider a situation, when we have some list of items with requirement that every item must be unique in the list and datasource have autoSync: false. The list contains item A already. We delete item A, then create the same item A and trying to sync() datasource. At one point the list will contain two A items, because kendo always executes Create before Destroy and I cannot find the way how to change this order from my code.

[Atanas Korchev]

Hello,

This is by design and cannot be changed at this point.

Regards,
Atanas Korchev
Telerik

 

 

[Salim]

I completly agree with Alexander. Was something done regarding the order of the Create, Update, Destroy?

[Stephen]

I stopped using the built-in sync() a while ago and submit all my grids with a variation of this technique: http://www.telerik.com/support/code-library/save-all-changes-with-one-request

 

This way, you have complete control of the order of the save, can validate across the entire resulting dataset(i.e. no duplicate rows), can have the create/update/delete inside a single DB transaction, etc.

[Salim]

This is what I did also. I used the submit event