Grid row reorder trigger Destroy transport

[StoyanGoranov]

Bug report

When a Grid's row is reordered and then the changes are saved - a Destroy request is sent to the server for the dataItem of the reordered row. This happens even though no changes are applied to dataItem of the reordered row.

Reproduction of the problem

1. Run this Telerik REPL or this Dojo
2. Reorder a row
3. Open the browser's Network Tab
4. Click the Save Changes button

Expected/desired behavior

The Grid should not request the reordered item to be perished from the backend.

Environment

• Kendo UI version: 2024.1.130

[palhal]

Maybe I've misunderstood the whole concept of this feature, but isn't what's written in Expected/desired behavior in this issue plain wrong? Shouldn't it be rephrased to

The Grid should not request the reordered item to be perished from the backend.

As stated here:

Note that the reordering operation is only a client-side operation and it does not reflect the order of any data that is bound to the server.

And if I'm right, how come this is still unplanned? This is a dangerous bug. I just implemented reordering in one of our grids and later found out that customers have accidentally deleted several rows, only because they reordered some rows and edited another, random row afterwards.

Please raise this to the highest priority, or at least provide a workaround.

[alestoya]

Reported in 1656516

[nelito987]

Reported in 1657767