MMM I don't think, but maybe, more likely you made some mistake.
You mean a grid nested in a grid?
if yes, nested grid should work, but are not adviced for performance issues, because you nest two devices that do changes tracking, so there is a kind of explosion of "stored old values". I advice to use a SortableListfor if you need to insert it into each
row of another grid. The SortableListFor can be used as a grid, it has sorting, paging, etc, but has no Changes tracking.
Anyway maybe the list is not bound because you have not included the name of the field containing the list among the fields whose old values need to be mantained by the grid, or simply you have done some name prefix error. Please show me your code.
Fields to be mantained can be specified with the toTrack parameter of the DataGridFor instruction. Below an example of use:
.../*previous parameters*/, toTrack: new FieldsToTrack<ToDoItem>().
Add(f => f.Code).Add(f => f.Name).Add(f => f.Description).Add(m => m.Important)
.Add(f => f.ToDoRoles).Add(f => f.ToDoRole))
I prepared the 1.4.0 version of the toolkit. Please send me your EMail adress, so I send you the bits. NOT HERE, use the contact form of my blog: http://www.dotnet-programming.com/contact.aspx