Hi all,
My UltraTree don't show the third Level of Object Hierarchie. The Object Tree is build by EntityFramework. Each Object has two different ListMembers of Objects. One is recursive declared as follows:
public partial class ECU_WorkpiecesGroups : global::System.Data.Objects.DataClasses.EntityObject {
public List <ECU_WorkpiecesGroups> ChildWorkpiecesGroupList {
get { LoadChildWorkpiecesGroups(); return ChildWorkpiecesGroups.ToList();
} // ChildWorkpiecesGroups is a EntityCollection of ECU_WorkpiecesGroups
}
While Debugging through the Object the List is fullfilled with the right Objects; While showing the Objects with UltraTree the Tree is broken on the third Level. What could be my Problem?
Greatings: Rudy
Hi,
There's not much information here to on.
What version of the tree are you using?
Have you tried binding some other control to the same data source to see if this is actually a problem with the tree or the data source itself? Try binding to a WinGrid and see if it shows all three levels, just as a test.
Hi
I started a testprojekt with the mentioned problem.
Recursive issues are quite different on ultratree and ultragrid.
On ultratree, dataset or entityset makes a difference, too.
The ultragrid shows the recursive data from the entityset without any matter on childdata ... The tree wants the binding for each node on each level of the tree ...
With a dataset the ultratree shows the recursive data without any matter on setting the childdata.With an entityset the ultratree needs the recursive data to be set for each level in the tree.
Am i missing a setting/property for the entityset?
Greetings from Germany
Dietrich
Hi Dietrich,
Oh, so your data source is recursive? That makes a big difference. There was a bug in the tree like this which was fixed a while back. You probably just need to get the latest service release.
How to get the latest service release - Infragistics Community
Hi Mike
Hmm ... i am not quite familiar with other sources than sql server.
You can try with any datasource, make a table with a relation on itself (id and parentid). Fill it with test data, like i've done on the save method ... and "feel" the difference on dataset vs. entity and ultratree and ultragrid.
Greetings from germany
Sorry, I don't know how I failed to see your sample there.
I just tried running it now, though, and it seems to be relying on a SQL Server which I cannot access, so I'm afraid I cannot run it.
Can you create some test data in code instead of relying on an outside server? Or maybe run the app and save the DataSet to a file using the Save method. Then you can load it into the application at run-time and remove the server dependency.
I posted a testproject in my reply before. It's an example studio 2010 project with ultratree and ultragrid.
I tried both entity and dataset.
Can you try the project and tell me if it works
I'm afraid I am not all that familiar with EntitySets. But there's no reason why the grid and the tree should behave differently. They both get the data from the BindingManager in essentially the same way, so it should not matter what the data source is or which control you are using.
If the grid shows the data correctly and the tree does not, then it may be a bug in the tree, or it might be the result of the way in which the tree automatically generates the ColumnSets.Perhaps the way in which the EntitySet generates the names of the bands is different than the way the DataSet does it.
If you can post a small sample project demonstrating the issue, we could certainly look into it and see what's going on.