Kendo UI kendo ui grid row disappears from the grid when cancel editing

[Plamen]

I have the following problem:
I have a kendoUI grid and I execute the following steps:

1. I add a row to the grid.

2. I click "Edit"

3. I click "Cancel"

The row disappears.

 

<script>
$("#grid").kendoGrid({
  columns: [
    { field: "name" },
    { command: ["destroy", "edit"]}
  ],
  dataSource: {

    schema: {
      model: { id: "id" },
      fields: {
              id: {type: "number"},
            name:  { type: "string", editable : true},
               }
    }, 
  },
  editable: {
    mode: "inline"
  }, 
   toolbar:[ "create"],
});
</script>

[Georgi]

Hi Plamen,

I have answered your inquiry in the support ticket. However, I will post the answer here as well in case someone from the community has the same issue.

===

Thank you for the provided code. The observed behavior is expected since id is key word for Kendo. For each data item an internal object in the data source is created. These objects extend the data objects passed to the grid. Since the internal objects also have id property, that property gets overridden by the values of the data objects.

Also clicking cancel executes the cancelChanges method. In other words all items with default identifiers are considered not saved and they get removed. So when creating item and the grid is bound to local data, an id have to be defined.

I have modified the provided code and now the Kendo Grid works as expected:

• http://dojo.telerik.com/ExiRI/4

===

As a side note, we monitor both the forums and the ticketing system. Please avoid submitting duplicate threads. That will enable us to keep better track of the support history and provide better service.


Regards,
Georgi
Progress Telerik

[stim]

Georgi,

One step more and your example doesn't work! Just do the following on an existing record:

1) Edit.

2) Change personId.

3) Update.

4) Edit.

5) Cancel.

Regards,
gz

[Georgi]

Hello Stim,

You are correct, the  behavior occurs when you modify the identifier. However, this is not quite a valid scenario as the user should not be able to modify the id field. Allowing it might cause more serious trouble.

Could you please share a bit more details on your case? Why is it necessary to allow the users to modify the ids of the items?

Regards,
Georgi
Progress Telerik

[stim]

The ID field determines a meaningful and changeable order of the items. We cannot easily modify the affected database tables to introduce, say, some surrogate IDs and the OrderNo fields because another application relies on the current schema (it's a legacy system).

Regards,

gz

[Plamen]

Georgi,

I am sorry I did not respond here earlier.

The id fixed it. Have been using it ever since!

Thank you!

[Georgi]

Hi Gz,

How do you handle updates for items which have their id modified? How do you map the sent object to the actual database item if the id field is no longer the same? Do you have another identifier field?

Regards,
Georgi
Progress Telerik

[Tony]

Hey Georgi, I'm not sure I fully understand the functionality. I'm working on the inline editing, but the way it is set up right now, if a user accidently edits the wrong record and hits cancel, that record disappears. Not optimal and not good for the user to see records disappear. It seems more like a bug. Looking forward to the help, thanks

[Georgi]

Hello Tony,

Would it be possible to share your configuration with us?

Clicking should not remove the edited item. Please check our demo where the item is not removed after clicking cancel:

• https://demos.telerik.com/kendo-ui/grid/editing-inline

Could you please make sure you have specified the dataSource.schema.model.id setting?

Regards,
Georgi
Progress Telerik

[Tony]

Thanks Georgi!

That seemed to fix the issue I was having. I didnt have the dataSource.schema.model.id. Out of curiosity, why does the component require that for it to work properly.

Thank you,

Tony

[Georgi]

Hi Tony,

The dataSource uses the id of the model to track its status. Internally we create a map which indicates the state of each item whether it is new, modified or saved. Without the any identification we are not capable of building this map, thus tracking the items is not possible.

Regards,
Georgi
Progress Telerik