I'm trying to figure out how to access parent level data using template syntax (#: parentId #) as opposed to data-bind="text: parentId" syntax. The data-bind syntax finds the parent data, but the template syntax does not. I'm trying to create a path so I cannot use data-bind syntax. I've created an example to demonstrate the problem here:
http://jsfiddle.net/MadCodeMonkey/uwf5w83x/
If you remove #: parentId # from the template, it will work again.
I assume that it is supposed to automatically retrieve parent data the way data-bind works, but perhaps it just doesn't work the same way.
3 Answers, 1 is accepted
Hello Dave,
the data-bind approach works because the observables automatically build object hierarchy, necessary for the change detection (and, for that matter, cases like this one) to be handled correctly. Apart from that, a "parent object" concept is not present in the plain javascript objects. They are not "aware" that an object has a reference of them bound to a given field.
Regards,
Petyo
Telerik
Rank 1
Petyo,
Thank you. I just wanted to make sure that I wasn't missing something. My work around currently is to pass along a copy of the parent fields to the child row objects when they are created on the client side. It's not ideal, but it works.
I did try putting the parent on the child object, but that generates a "Uncaught RangeError: Maximum call stack size exceeded" error.
Dave
Hello Dave,
Indeed, this is so - assigning the parent to child will produce circular reference, which in many cases trips the JSON serializer.
Regards,
Petyo
Telerik