{"id":2379,"date":"2014-09-28T09:42:16","date_gmt":"2014-09-28T09:42:16","guid":{"rendered":"http:\/\/putridparrot.com\/blog\/?p=2379"},"modified":"2018-04-23T19:00:10","modified_gmt":"2018-04-23T19:00:10","slug":"displaying-hierarchical-data-in-infragistics-xamdatagrid","status":"publish","type":"post","link":"https:\/\/putridparrot.com\/blog\/displaying-hierarchical-data-in-infragistics-xamdatagrid\/","title":{"rendered":"Displaying Hierarchical data in Infragistics XamDataGrid"},"content":{"rendered":"

Before I start this post, let me just say I’m using an old version of the Infragistics XamDataGrid for this post, version 10.3. Hence this may have been changed in subsequent releases, but as I have a legacy application to support, that’s the version we’re using.<\/em><\/p>\n

I want to display hierarchical data within the grid, so let’s start with a sample view model.<\/p>\n

\r\npublic class EmployeeViewModel\r\n{\r\n   public EmployeeViewModel()\r\n   {\r\n      Manages = new ObservableCollection<EmployeeViewModel>();\r\n   }\r\n\r\n   public string Name { get; set; }\r\n   public ObservableCollection<EmployeeViewModel> Manages { get; set; }\r\n}\r\n<\/pre>\n
Note: I’ve not bothered with supporting the INotifyPropertyChanged interface etc. this is bare bones just to demonstrate the concepts<\/em><\/p>\n
So the EmployeeViewModel represents a basic employee hierarchy. Here’s a factory that creates the same data, which should make the hierarchy quite obvious.<\/p>\n
\r\npublic static class EmployeeViewModelFactory\r\n{\r\n   public static ObservableCollection<EmployeeViewModel> Create()\r\n   {\r\n      var employees = new ObservableCollection<EmployeeViewModel>();\r\n\r\n      var bob = new EmployeeViewModel {Name = "Bob"};\r\n      var bill = new EmployeeViewModel { Name = "Bill" };\r\n      var fred = new EmployeeViewModel { Name = "Fred" };\r\n      var alfred = new EmployeeViewModel { Name = "Alfred" };\r\n      var jim = new EmployeeViewModel { Name = "Jim" };\r\n      var jeff = new EmployeeViewModel { Name = "Jeff" };\r\n      var craig = new EmployeeViewModel { Name = "Craig" };\r\n\r\n      bob.Manages.Add(bill);\r\n      bob.Manages.Add(fred);\r\n\r\n      alfred.Manages.Add(jim);\r\n\r\n      jim.Manages.Add(jeff);\r\n\r\n      employees.Add(bob);\r\n      employees.Add(alfred);\r\n      employees.Add(craig);\r\n\r\n      return employees;\r\n   }\r\n}\r\n<\/pre>\n
Now it’s pretty easy to configure the XamDataGrid to handle this data, I’ll manually create the fields, so here’s the XAML<\/p>\n
\r\n<igDP:XamDataGrid GroupByAreaLocation="None" DataSource="{Binding}">\r\n\r\n   <igDP:XamDataGrid.FieldLayoutSettings>\r\n      <igDP:FieldLayoutSettings ExpansionIndicatorDisplayMode="CheckOnDisplay"\r\n                                          AutoGenerateFields="False"\/>\r\n   <\/igDP:XamDataGrid.FieldLayoutSettings>\r\n\r\n   <igDP:XamDataGrid.FieldLayouts>\r\n      <igDP:FieldLayout>\r\n         <igDP:FieldLayout.Fields>\r\n            <igDP:Field Name="Name" \/>\r\n            <igDP:Field Name="Manages" Visibility="Hidden" \/>\r\n         <\/igDP:FieldLayout.Fields>\r\n      <\/igDP:FieldLayout>\r\n   <\/igDP:XamDataGrid.FieldLayouts>\r\n\r\n<\/igDP:XamDataGrid>\r\n<\/pre>\n
This will produce the following UI<\/p>\n
\"XamDataGrid<\/p>\n
This is great, but I don’t really want the subheadings for this data and I’d prefer if the child columns lined up with the parents, more like a treeview and this is where things get a little tricky.<\/p>\n
Removing the child item headers<\/strong><\/p>\n
To remove the headers we use<\/p>\n
\r\n<igDP:FieldLayout.Settings>\r\n   <igDP:FieldLayoutSettings LabelLocation="Hidden" \/>\r\n<\/igDP:FieldLayout.Settings>\r\n<\/pre>\n
This code is placed within the FieldLayout section, but ofcourse if you do this in the one and only FieldLayout you’ll also lose the heading of the parent row.<\/p>\n
So what you might try is to implement a second FieldLayout section as per <\/p>\n
\r\n<igDP:XamDataGrid.FieldLayouts>\r\n   <igDP:FieldLayout>\r\n      <igDP:FieldLayout.Fields>\r\n         <igDP:Field Name="Name" \/>\r\n         <igDP:Field Name="Manages" Visibility="Hidden" \/>\r\n      <\/igDP:FieldLayout.Fields>\r\n  <\/igDP:FieldLayout>\r\n\r\n  <igDP:FieldLayout>\r\n     <igDP:FieldLayout.Settings>\r\n        <igDP:FieldLayoutSettings LabelLocation="Hidden" \/>\r\n     <\/igDP:FieldLayout.Settings>\r\n     <igDP:FieldLayout.Fields>\r\n        <igDP:Field Name="Name" \/>\r\n        <igDP:Field Name="Manages" Visibility="Hidden" \/>\r\n     <\/igDP:FieldLayout.Fields>\r\n   <\/igDP:FieldLayout>\r\n<\/igDP:XamDataGrid.FieldLayouts>\r\n<\/pre>\n
But this will not<\/strong> solve the problem and here’s the gotcha…<\/p>\n
From my understanding the FieldLayout is based upon the the field names on your objects and hence as the EmployeeViewModel is used throughout only the first FieldLayout is ever applied to the view of the data. For example even if you changed all top level employees in the example to be of type ManagerViewModel (with this being an exact copy of EmployeeViewModel, and obviously fixing the code to handle this in the factory etc., you would still find only the first FieldLayout used. On the other hand if we had something like <\/p>\n
\r\npublic class ManagerViewModel\r\n{\r\n   public ManagerViewModel()\r\n   {\r\n      Manages = new ObservableCollection<EmployeeViewModel>();\r\n   }\r\n\r\n   public string Name { get; set; }\r\n   public ObservableCollection<EmployeeViewModel> Manages { get; set; }\r\n}\r\n\r\npublic class EmployeeViewModel\r\n{\r\n   public EmployeeViewModel()\r\n   {\r\n      DepartmentManages = new ObservableCollection<EmployeeViewModel>();\r\n   }\r\n\r\n   public string Name { get; set; }\r\n   public ObservableCollection<EmployeeViewModel> DepartmentManages { get; set; }\r\n}\r\n\r\npublic static class EmployeeViewModelFactory\r\n{\r\n   public static ObservableCollection<ManagerViewModel> Create()\r\n   {\r\n      var employees = new ObservableCollection<ManagerViewModel>();\r\n\r\n      var bob = new ManagerViewModel { Name = "Bob" };\r\n      var bill = new EmployeeViewModel { Name = "Bill" };\r\n      var fred = new EmployeeViewModel { Name = "Fred" };\r\n      var alfred = new ManagerViewModel { Name = "Alfred" };\r\n      var jim = new EmployeeViewModel { Name = "Jim" };\r\n      var jeff = new EmployeeViewModel { Name = "Jeff" };\r\n      var craig = new ManagerViewModel { Name = "Craig" };\r\n\r\n      bob.Manages.Add(bill);\r\n      bob.Manages.Add(fred);\r\n\r\n      alfred.Manages.Add(jim);\r\n\r\n      jim.DepartmentManages.Add(jeff);\r\n\r\n      employees.Add(bob);\r\n      employees.Add(alfred);\r\n      employees.Add(craig);\r\n\r\n      return employees;\r\n   }\r\n}\r\n<\/pre>\n
and the XAML might look like<\/p>\n
\r\n<igDP:XamDataGrid GroupByAreaLocation="None" DataSource="{Binding}">\r\n   <igDP:XamDataGrid.FieldLayoutSettings>\r\n      <igDP:FieldLayoutSettings ExpansionIndicatorDisplayMode="CheckOnDisplay"\r\n                 AutoGenerateFields="False"\/>\r\n   <\/igDP:XamDataGrid.FieldLayoutSettings>\r\n   <igDP:XamDataGrid.FieldLayouts>\r\n   <igDP:FieldLayout>\r\n      <igDP:FieldLayout.Fields>\r\n         <igDP:Field Name="Name" \/>\r\n         <igDP:Field Name="Manages" Visibility="Hidden" \/>\r\n      <\/igDP:FieldLayout.Fields>\r\n   <\/igDP:FieldLayout>\r\n\r\n   <igDP:FieldLayout>\r\n      <igDP:FieldLayout.Settings>\r\n         <igDP:FieldLayoutSettings LabelLocation="Hidden" \/>\r\n      <\/igDP:FieldLayout.Settings>\r\n      <igDP:FieldLayout.Fields>\r\n         <igDP:Field Name="Name" \/>\r\n         <igDP:Field Name="DepartmentManages" Visibility="Hidden" \/>\r\n      <\/igDP:FieldLayout.Fields>\r\n   <\/igDP:FieldLayout>\r\n   <\/igDP:XamDataGrid.FieldLayouts>\r\n<\/igDP:XamDataGrid>\r\n<\/pre>\n
We would now see the following<\/p>\n
\"XamDatdGrid<\/p>\n
Not ideal, but we now know why EmployeeViewModel referencing itself in the Manages property fails to work. However we now have some more oddities, including the fact that the column lines are out of alignment. I’ll be writing another post on my attempts to resolve this.<\/p>\n
References<\/strong><\/p>\n
Can I choose a field layout based on data Type?<\/a>
\nFieldLayout Class<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Before I start this post, let me just say I’m using an old version of the Infragistics XamDataGrid for this post, version 10.3. Hence this may have been changed in subsequent releases, but as I have a legacy application to support, that’s the version we’re using. I want to display hierarchical data within the grid, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[84,85],"tags":[],"class_list":["post-2379","post","type-post","status-publish","format-standard","hentry","category-infragistics","category-xamdatagrid"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/2379","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=2379"}],"version-history":[{"count":15,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/2379\/revisions"}],"predecessor-version":[{"id":6182,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/2379\/revisions\/6182"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=2379"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=2379"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=2379"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}