I have gridView defined inside a DataTemplate for a TabControl.
Within this GridView I have a column that I need to provide a list of choices from over 200 records with multiple columns, that needs to be filterable, so I thought either a button that brings up a popup window, or using a combobox with a gridview. Either solution requires me to bind to properties on my viewmodel for the list of 200+ records.
Controls inside the DataTemplate defined for the TabControl are bound to the VM by setting a name on the UserControl and binding to {DataContext.Property, ElementName=MyUserControl}. This works, until I get to the DataTemplate that is defining the CellEditTemplate. I thought I could use the same method for declaring my binding, but it just isn't working.
Is there a heirarchy limit I'm reaching, but having a DataTemplate defined inside of a DataTemplate?
Within this GridView I have a column that I need to provide a list of choices from over 200 records with multiple columns, that needs to be filterable, so I thought either a button that brings up a popup window, or using a combobox with a gridview. Either solution requires me to bind to properties on my viewmodel for the list of 200+ records.
Controls inside the DataTemplate defined for the TabControl are bound to the VM by setting a name on the UserControl and binding to {DataContext.Property, ElementName=MyUserControl}. This works, until I get to the DataTemplate that is defining the CellEditTemplate. I thought I could use the same method for declaring my binding, but it just isn't working.
Is there a heirarchy limit I'm reaching, but having a DataTemplate defined inside of a DataTemplate?