Inline editing Cancel removes the row

[Just]

I've a page that has a Kendo grid. The grid has a hyperlink column. On click of hyperlink I show a modal popup that has another kendo grid.

In the second grid (within the popup) I've inline editing enabled.
Two problems:
a.) I have a field defined as editable:false and it still is editable on edit click.

{field:"SettingName", title:"Setting Name", filterable: false, width: 200, editable:false }

b.) MAJOR:: I click "Edit" -> the row becomes editable. And then I hit "Cancel". And the row disappears from the grid!!! This has me confused. What could be happening here? Has anybody else observed it?

Thanks.

[tan]

hey,i hava the same problem.any body know it ....if you have solution.pls write it here.

[tan]

i solves it by define a property id....so. i was new in kendo and i wasn't notice the id must be given property.

[Jason]

do you have the code you added to the js file to stop the cancel button from removing the row??..


Nevermind.. I figured it out.. ty.. :)

[JORGE CRISOSTOMO]

This happened to me too. I looked up the code and it does a filter after a cancel using uid.
I noticed that my definition for the datasource have a type:

schema: {
                    model: {
                        Id: "Id",

The Id is spelled as capital I then d.

I updated it to:
schema: {
                    model: {
                        id: "Id", 
all small caps and it worked as it should. Check your model definition for case typos.

[Kristin]

I currently have a field called "id" and am still having this issue as well.    Every time I hit 'cancel', it still removes the row and I am stumped as to why it's doing it.  Any thoughts???  Here is my code:

   

$("#tblTrucks").kendoGrid({

    dataSource: {

        data: trucks,

        schema: {

            model: {

                fields: {

                    id: { type: "string", validation: { required: true} },

                    license: { type: "string", validation: { required: true} },

                    truckcoid: { type: "string", validation: { required: true} },

                    truckid: { type: "string", validation: { required: true} },

                    enabled: { type: "boolean" }

 

                }

            }

        }

 

    },

    columns: [

        { field: "id", title: "ID", width: "60px" },

        { field: "license", title: "License", width: "85px" },

        { field: "truckcoid", title: "TruckCoId", width: "90px" },

        { field: "truckid", title: "TruckID", width: "75px" },

        { field: "enabled", title: "Enabled", width: "80px" },

        { command: ["edit", "destroy"], width: "190px" }

    ],

    editable: "inline",

    toolbar: ["create"]

 

});

[Just]

Try putting your Id before the fields declaration. Like this

schema: {

            model: {

                 id: "MyIdField",
fields: {

[Kristin]

This worked!  Thank you so much!

[s]

i also have this problem but your solution doesn't work on me 

<div data-role="grid"<br>                     data-editable="inline"<br>                     data-toolbar='[{name:"create", text:"Add"}]'<br>                     data-columns="[{ field: 'name', title:'Name'},<br>                                     { field: 'url', title:'Url'},<br>                                     {command: ['edit','destroy'], width: '200px'}]"<br>                     data-source="{ schema: {<br>                                            model: {<br>                                                    id:'id',<br>                                                    fields:<br>                                                    {<br>                                                    id: { editable: false},<br>                                                    name: { type: 'string' },<br>                                                    url: { type: 'string' }<br>                                                    }<br>                                                   }<br>                                            }<br>                                  }"<br>                     data-bind=" source :details.links" />

[CS]

I have the same problem with my grid, id is set and everything but the row is removed from the grid. But my custom destroy function is not used for this but the standard one that only removes a row, at least it seems so.

[CS]

I think I found a solution, at least it works for me. I have no idea if that is the intended use, but when you give the model an id with the name of one of your fields properties it seems to work. 

[Nikolay Rusev]

Hello Stefan,

The model `id` is a *must* in order to have state tracking correctly. It is internally used for checking whether the model instance is `new` or `existing`.

Regards,
Nikolay Rusev
Telerik

 

 

[CS]

The problem is that the id seems to need to match with one of the field property names in order to work correctly. I assumed I can freely choose a name for the id.

[Nikolay Rusev]

Hello Stefan,

Yes, `id` field must be actual field from the model.

Regards,
Nikolay Rusev
Telerik

 

 

[Kenneth]

It appears there is a case sensitive issue here.  If I use the following in my datasource (note the captial "I" in Id to make it different from the model id), all is well and the Cancel button just cancels the operation and leaves the row in tact.

schema: {
  model: {
    id: "Id",
    fields: {
      Id: { type: "number", validation: {required: true } },
...

If I instead name my field "id" (lowercase) the Cancel button acts like a delete button and the row is removed:

schema: {
  model: {
    id: "id",
    fields: {
      id: { type: "number", validation: {required: true } },
...

I really didn't expect that "feature".

[Nikolay Rusev]

Hello Kenneth,

 

JavaScript syntax is case sensitive. Word casing does matter and you should be careful when defining fields name.

 

Regards,
Nikolay Rusev
Telerik

 

 

[Kenneth]

Thank you Nikolay.  Understood.  However, I've seen developers commonly use "id" as a database field name (usually the primary key) on database tables.  I would either add a note to the documentation or throw a configuration error from the control if the field "id" is used since it is a reserved name.

[Benny]

Thanks a lot. It works