If I have a node in a HierarchicalDataSource, and I want to sync changes to it, I assume I should call
When I call this, the resulting data packet contains, as its 'id' property, the id of the parentNode, not of the child.
This seems to be due to the fact that kendo.data.Node's _initChildren function indiscriminately applies the parent's identity to the request's data object.
Clearly, that makes no sense for update/delete actions, where some other property would make more sense, or the ability to include or not include the parent property.
Arguably, the entire path should be available, for situations where a node can exist in multiple places in the tree.
I suppose I could overcome this with the data: property being a function, but I think the basic assumption is mistaken.