Hello,
I have a table with an AccountID column and a ParentID column. There is a data relation, Children, that relates the columns. Below is the xaml I have written to try and get it to work, but when I add the <igDP:Field Name="Children" /> field, only the second FieldLayout is displayed, and the first FieldLayout disappears. What do I need to change to get this to work? Does the hierarchical stuff only work with multiple tables?
<igDP:XamDataGrid.FieldLayouts> <igDP:FieldLayout> <igDP:FieldLayout.Fields> <igDP:Field Name="Name" /> <igDP:Field Name="Type" /> <igDP:UnboundField Name="Balance" DataType="system:Decimal"/> <igDP:Field Name="Inactive" Visibility="Collapsed" /> <igDP:Field Name="Children" /> </igDP:FieldLayout.Fields> </igDP:FieldLayout> <igDP:FieldLayout> <igDP:FieldLayout.Fields> <igDP:Field Name="Name" /> <igDP:Field Name="Description" /> </igDP:FieldLayout.Fields> </igDP:FieldLayout>
I have a similar issue... but a variation of it ...
Here is what I have:
Here is what I want: Simple, but oh well don't get me started:
Ok, show me the easiest and fastest way there....
Thanks
Thank you for NO support. As of Friday we have chosen to dump Infragistics WPF controls and have adopted a different product.
Cheers....
We have accomplished this with the system we are currently building. I have been able to use the XamDataGrid to mimic a tree view using a single, self referencing table of Parent-Child relationships to an Nth level of Parent - Child relationships.
However there is no magic and it did take lots of C# code, XAML, and SQL to accomplish. If someone is still interested I might be able to help.
Cheers.....
I attached an example of binding the xamDataGrid with DataSet and LINQ with self-relation.
Hi Donna,
Can you mail me the sample app, to gautham82@gmail.com
I would share but it is complicated and relies on a SQL Recursive CTE to generate the initial hierarchical structure. The hierarchy structure uses ParentID, WbsLevel, WbsSequence fields to create a grid record key that can be used as the sort column in the XamDataGrid to keep it in hierarchical sequnece. Also a custom "ExpandGridrowButton" that Curtis from Infragistics helped me create to show or hide child gridrows based on HasChildren and RecVisible fields to get functionality similar to a tree view. Also functionality to create children, parents, move units and children withn the hierarchy.
To create a sample I can send as a project would be a project in itself. Currently I am under a deadline to get version 1 of the system developed by March 31 and cannot spend time creating a portable sample. I am sorry if this is a lame excuse but right now it is a reality for me. I have done a lot of work on this to de-bug and it is possible that by May I would have time to create a portable sample that worked off a dataset.
I would like to see your sample if possible, and I am sure there are lots of other people that would like to see too.
Thanks,
Joe
Of course -- sharing the sample (if you have the time and permissions to do that) -- will certainly benefit a lot of felow developers. We do recognize that self-referencing relations is something that is common in the real world and will do our best to create more samples in xamFeatureBrowser and in the online help that covers this topic. In addition to LINQ and DataSets, we are also working on a sample that covers self-referencing relation from a database (single table with ID -> ParentID relation) that gets mapped into an ObservableCollection and then loaded in the grid.
Of course we would prefer to see you approach, since it can be potentially better / better tested / time proven.
Thanks a lot for your desire to share in public forums - much appreciated.
I have a model that works for me. I also am willing to share. I am not using Datasets but the actual Business Objects themselves.
I guess I was irked by the guys e-mail. Build my app for me, fast and easy, and I will buy your products. There is always a way to do something and but it is not always "fast and easy". Sometime there is not a sample to copy and you actually have to think and develop a model of your own.
Imagine, a developer actaully developing instead of copying the sample.