I've noticed that when you map the id of the model to a different field (e.g. id: "personID") , the resulting object will actually possess still possess the ID field as well as whatever it was assigned to.
e.g. using the personID example
var test = kendo.data.Model.define({id: "personID"});
t = new test();
Results in:
{personID: "", uid: "a30e1c16-fc65-4345-980c-4d5ad527348c", dirty: false, id: ""}
My question is what it the use of the id field versus the personID field. I've noticed the framework updates both fields upon a successful post back. but also that the isNew() function only tiggers of the id field... not the personID field.
e.g. using the personID example
var test = kendo.data.Model.define({id: "personID"});
t = new test();
Results in:
{personID: "", uid: "a30e1c16-fc65-4345-980c-4d5ad527348c", dirty: false, id: ""}
My question is what it the use of the id field versus the personID field. I've noticed the framework updates both fields upon a successful post back. but also that the isNew() function only tiggers of the id field... not the personID field.