Since our latest update of Infragistics (2010v2 2109) the excel exporting has been a bit strange.
Column Header Rows are displayed on every row. I've attached an image to show this.
I've added a temporary work around for this for the moment.
After looking through export events I found the "GridExportCache.BandZeroHeaderExportedForGroupIsland" boolean was never flagged as true.
Another variable that is seemlingly helpful is the "PlacedHeadersOnTop" boolean..Anyway. Is there a flag that needs to be set for this to occur?
Thanks.
I did solve the problem, thank you!
As for Excel row expansion.. I decided it would be easier to navigate using the layers rather than the expansion indicators.
Cheers.
Hi,
I just wanted to know if you were able to solve your issue based on my or Mike's suggestions or you still need help? Just let me know.
Thank you.
Hello ,
I am not sure where are you trying to export your UltraGrid to PDF or to Excel? if you are talking about exporting to PDF and if you want to prevent child rows exporting of collapsed row, you could handle OnRowExporting event of UltraGridDocumentExpoter and put there following lines of code :
if (!e.GridRow.IsExpanded)
e.GridRow.Hidden = true ;
If you are talking about the excel exporting I have tried to export an UltraGrid to excel using 10.2 2109 and in the exported file all rows, which could be expanded, were collapsed. So please let me know if I am missing something.
Let me know if you have any further questions.
Most grids have multiple bands and to my knowledge no header placements have been set anywhere in the system. We use the default value.
I've modified the code the set the band header placement and it works as expected. Thanks!
One more question while I'm on the subject. Every row in an exported grid is expanded regardless of my efforts to stop it from doing so. What needs to be set to do this?
We recently updated the UltraGridExcelExporter to honor the HeaderPlacement property on the grid's Override object. It did not previously honor this property setting, which was a bug.
So this is probably what caused the change in behavior you are seeing here. But I can't be sure if this behavior is a bug we introduced or if this is just a result of the situation you have in your application.
Does your grid have multiple bands? Is there a child band in the data source? Are you setting HeaderPlacement? If so, what are you setting it to?