I had this working with the Ultratree, but it's stopped working. The dataset is complex w/ multiple relations off the same table. One of them is recursive, and that is what I want to show in the tree. It refuses now to show the recursive relation, where it was showing it before I added other relations. I'm extremely frustrated with this and under a time crunch.
Any help would be appreciated.
What's breaking this are other relations within the dataset--relations to other tables within the dataset. I don't want these relations in the tree, so I've deleted them from the columnsets, but that doesn't make any difference. The other thing is if I set ShowBandNodes to "always" it'll show the recursed nodes with separator bands, which I don't want because it adds unnecessary levels to the tree.
Hi Jeff,
The ColumnSets in the tree are very powerful and give you a lot of control, but they can be a little tricky to work with.
The ColumnSets are associated with bands of data via the Key of the ColumnSet. The tree tries to match up the key of the ColumnSet with the name of the band. So if your bands don't all have names, then an empty string might be getting matched up to multiple bands.
It's impossible to say exactly what the problem is without knowing more, but when I debug something like this, I start by handling the ColumnSetGenerated event and looking at the ColumnSet and columns that are being generated. In a recursive situation, you will probably only need one or two column sets and that column set needs to have a column which represents the child band - this column will have the IsChaptered prpoerty set to true. Make sure you don't remove this column or change IsChaptered to false, since that will remove/hide the child band.
If you can duplicate the behavior in a small sample project and submit it to Infragistics Developer Support, they should be able to see what's going on and why the child data isn't showing up.
http://devcenter.infragistics.com/Protected/SubmitSupportIssue.Aspx