Hi,
I need to create a grid with up to 20 or 30 child bands levels to display read only hierarchical dataI do not want to use ultratree to be able to benefit from ultragrid excel export and print built-in functionnalities.The issue I have is that when binding the datasource to the grid it is very slow.I can reproduce the issue with the virtual mode samplevar band = this.ultraDataSource1.Band; for (int i = 0; i < 20; i++) { UltraDataBand childBand = band.ChildBands.Add(i.ToString()); childBand.Columns.Add("Prime Factors", typeof(string)); band = childBand; } // Set grid's data source to the ultra data source that we just setup. this.ultraGrid1.DataSource = this.ultraDataSource1;
The last line of code is very slow to perfom even if do not have any actual data in the datasource.Is there any recommandations or workaround to do this.
Thanks in advance
Hi ffimbel,
I have come across a knowledge base entry that I believe you may find useful; wherein the procedure for exporting the contents of the UltraTree to Excel is documented with sample code.
You may find the article by following this link, http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=10055
In the meantime, I have submitted a Product Idea on your behalf for Exporting and Printing functionality to be extended from the UltraTree. I have submitted this request directly to my product management team.
Our product team chooses new product ideas for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.
We value your input, and our philosophy is to enhance our toolset based on customer feedback. If your feature is chosen for development, you will be notified at that time. Your reference number for this Product Idea is PI12040106.
If you would like to follow up on your product idea at a later point, you may contact Developer Support management via email. Please include the reference number of your product idea in the subject and body of your email message. You can reach Developer Support management through the following email address: dsmanager@infragistics.com
If you have any further questions regarding this request, please let us know.
Sincerely,Chris KDeveloper Support EngineerInfragistics, Inc.www.infragistics.com/support
Hi Franck,
ffimbel said:Is there any plan to implement printing and excel export to the ultratree component as if think sa would be a better choice for my case.
There hasn't been any announcement about any such plans. But you should Submit a feature request to Infragistics.
Printing would be pretty tough to implement yourself, but it wouldn't be too tough to use the Infragistics Excel library to write export the tree yourself. It's just a matter of looping through the tree nodes and writing that information to Excel.
Thanks for those answers.The perfomance guides helped me a little but I still have the issue when binding source to the grid with 20 bands. As it is not a so usual user case I will stick with the grid.
Is there any plan to implement printing and excel export to the ultratree component as if think sa would be a better choice for my case.
Franck
30 child bands is pretty steep. No human user could possible deal with so much data all at once. So my first recommendation would be to break up the data and present it to the user in smaller chunks if you possibly can - just to provide them with a better UI.
If you must display that much data in a single grid, then there are a number of reasons why it might be slow with this much data. I recommend that you check out the WinGrid Performance Guide. There is a lot of advice there on how to make your grid more efficient.
Also, there is a follow-up discussion here with a discussion of data sources.
If none of that helps you, see if you can post a small sample project demonstrating the issue, and I will be happy to take a look at it and see if I can find out what's going on.
This is what we found. After 15'ish or maybe a few more bands, the grid was unusable. Brought it up with support who were unable to help out, kind of like 'it is what it is'. Had to find another vendor for hierarchical grid support.