Hello,
I have a parent/child data structure that i want to display in two separate grids. As the user scrolls through the parent grid, the related child records will be displayed in the child grid. All the examples I've seen use the hierarchical grid, but I prefer not to use that method. Can anyone provide guidance or point me to some examples.
Thanks,
Steve
Hello Steve,
I'm afraid that I could not understand your requirement. There are only two available IgniteUI grid controls that represent a data with hierarchical structure and they are igHierarchicalGrid and igTreeGrid. Could you please let me know why igHierarchicalGrid is not suitable for you?
Regards,Tsanna
The hierarchical grid often isn't suitable for a variety of reasons, a common one among many users I've worked with is that they just don't like it. The most common reason is that it's difficult to line up columns with column headers when you're trying to analyze or compare data.
A common scenario includes a collection of custom business objects (usually a List or BindingList) where each item in the collection contains one or more child collections (again, List or BindingList of custom business objects). In many scenarios, we have multiple types of child collections for each parent, and sometimes we even have parent/child/grandchild relationships.
I've used the WPF controls extensively. With those controls, I can create two different xaml grids where the parent grid is bound to the parent collection, and the child grid is bound to the child collection of the active record in the parent grid. I'd like to replicate that pattern with the IgniteUI igGrid control, but I'm having trouble finding examples of anything like that. I'm hoping someone can point me towards some example, or some documentation that describes this pattern.
As I understand from your description, you want parent and child grids to be positioned one below other without this space for the expand indicator. Is this how you want the hierarchical grid to look like? About the issue related to the parent and child data that you mentioned, you may use two different datasource objects with a common key for the parent-child relation. However please note that in this case the child datasource will be loaded on demand. Attached is a sample for your reference. If I can provide you with further assistance, please let me know.
Regards,
Tsanna