Hi,
We're having trouble with certain grids when exporting to Excel. Randomly, it appears (size of list matters, but it seems only because it increases the chance of it happening).
I think the error is in a shared library (shared between the Web and Win components), and in the Web forums Mike Dour mentions that the issue is resolved in the next service release.
http://news.infragistics.com/forums/p/58193/301154.aspx#301154
I was hoping to get confirmation that 1) this is the same issue, and 2) it'll be bundled in the next SR of the win components as well. Also, some general timing on when that SR will be available would be helpful.
Thanks in advance!
Chris
Here's my stack trace:
at Infragistics.Documents.Excel.GenericElementHashSet`1.AddIfItemDoesntExist(T element, T& existingElement) at Infragistics.Documents.Excel.GenericCachedCollection`1.FindOrAdd(T element, T& equivalentElement) at Infragistics.Documents.Excel.GenericCacheElement.FindExistingOrAddToCache[T](T newElement, GenericCachedCollection`1 collection) at Infragistics.Documents.Excel.WorksheetCellBlock.SetCellValueInternalHelper(WorksheetRow row, Int16 columnIndex, Object valueInternal, DataType& type, CellValue& cellValue) at Infragistics.Documents.Excel.WorksheetCellBlock.SetCellValueInternal(WorksheetRow row, Int16 columnIndex, Object newValueInternal, Boolean checkForBlockingValues) at Infragistics.Documents.Excel.WorksheetRow.SetCellValueInternal(Int16 columnIndex, Object valueInternal, Boolean checkForBlockingValues) at Infragistics.Documents.Excel.WorksheetRow.SetCellValue(Int32 columnIndex, Object value) at Infragistics.Documents.Excel.WorksheetCell.set_Value(Object value) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter.SetRegionRelativeToOrigin(UltraGridExporterHelper exportHelper, Rectangle rect, Object val, IWorksheetCellFormat cellFormat) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter.WriteValueCell(UltraGridExporterHelper exportHelper, UltraGridRow row, UltraGridColumn ugColumn, Rectangle valueCellRect) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter.ExportRowValuesCells(UltraGridExporterHelper exportHelper, UltraGridRow row) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter.WriteSingleRow(UltraGridExporterHelper exportHelper, UltraGridRow row) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter.ProcessSingleRow(UltraGridExporterHelper exportHelper, UltraGridRow row) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter.ProcessGridRowInternal(UltraGridExporterHelper exportHelper, UltraGridRow row, ProcessRowParams processRowParams) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExporterHelper.ProcessRow(UltraGridRow row, ProcessRowParams processRowParams) at Infragistics.Win.UltraWinGrid.RowsCollection.InternalTraverseRowsHelper(IUltraGridExporter exporter) at Infragistics.Win.UltraWinGrid.UltraGrid.Export(IUltraGridExporter exporter) at Infragistics.Win.UltraWinGrid.ExcelExport.UltraGridExcelExporter.Export(UltraGrid grid, Worksheet worksheet, Int32 startRow, Int32 startColumn) at CTEC.DR.v40.Framework.ExportTemplateControl.ExportGrid(Worksheet _gridWorksheet) in D:\Projects\DR4x\4.0\Development\Framework\Shared\Controls\ExportTemplateControl.vb:line 144
Oops, realized I trimmed off the exception message itself:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
Thanks again,
This bug was already submitted and fixed (bug id 82020) on 7/21/11. I believe the SR with this fix has already gone out, so you could probably fix this by upgrading to the latest SR for the version you're using.
Hi Ganesh,
I looked up that bug ID and this was apparently fixed in 11.1.20111.2022. Now... that version number is an internal one, so that might not be the exact version of the Service Release. But the bug is essentially fixed in that version and up. So any SR with a higher version than that should be good.
Regarding verifying the fix, I can't think of any simple way to do that. The original poster (above) included a sample project by which we could duplicate the issue so we could get it fixed. But his sample includes an Excel file and I can't send you that because it might violate his privacy.
Hello Mike,
It would be a great help if you could let me know the exact SR number for Infragistics3.Documents.Excel.v11.1 - 11.1.20111.2009.
I couldn't find a way to confirm it. Also in my case this error appears for a specific data set that in Live environment. Is there any way to consistently reproduce this behavior so that I could test this in DEV, TEST environment before deploying it in Live?
Thank you in advance,
Ganesh.