i have a grid that exports fine as long as it is not grouped. the exporter and the code behind are using essentially the code from here
http://help.infragistics.com/Help/NetAdvantage/Silverlight/2011.2/CLR4.0/html/xamGrid_Asynchronous_Export_to_Excel.html
when i allow grouping the grid will not export. it also fails to through the exception in the catch. if i debug and step through i can capture it
mesage
"There was an error generating the XML document."
Innerexception
"Exception of type 'System.OutOfMemoryException' was thrown."
i do not understand why this is occuring, it is not in the known issues for export
any help would be apprciated
Hello,
Thank you for your post. I have been looking into the issue that you have described and I could not managed to reproduce it. I have created a sample application in order to test the exporting of the XamGrid into excel, using the asynch method when there is grouping applied to the grid and I have managed to export 10000 group rows into an excel worksheet. I have tested the sample application using the latest service release of version 12.1. I am attaching the sample application that I have created and the MS Excel document which is result of the exporting of the XamGrid.
Please let me know if you can reproduce the same issue with my sample application or I have misunderstood your scenario in any way.
Looking forward to hearing from you.
Sincerely,
Krasimir
Developer Support Engineer
Infragistics
www.infragistics.com/support
so for giggles i pulled the code out of you sample. i re wrote my page to use your exporting piece of it. got the same error message
There was an error generating the XML document
yes
wrote an entirly new app with new data, wouldnt you know it export still failed when i group thing
to say this would be high importance would be an understatement
excpetion thrown
An unhandled exception of type 'System.StackOverflowException' occurred in mscorlib.dll
on this line
this.excelExporter.ExportAsync(this.dg, workbook);
Hi spicish2222,
Can you give me the stack trace for that exception and the version number of the assemblies you are using? There was an issue in 12.1 similar to this where including the UndoManager from the UndoRedo framework caused a StackOverflowException when exporting to excel. I want to see if the issues are related.
i need a response on this. i have now put out a grid in production that i couldnt include grouping and still fails with the system out of memeory excption
You're using the RTM version of 11.2 then if those are the assembly versions being used in your application. I suggest updating to the latest service release of NetAdvantage for Silverlight which is on version 11.2.20112.2199 for the Silverlight 5 version. https://ko.infragistics.com/my-account/keys-and-downloads/
I've tried reproducing the issue previously but have had no luck so at this point if upgrading to the latest service release does not resolve the issue I'm going to need a sample from you that reproduces this.
i can not upgrade to SL 5 until the compnay says so, so i must stay at SL 4. if you can not support you product please let me account rep know as i may have to return this product
it is an utter failure, basically completely untested
Do you mean if they are easy to uninstall? They can be removed from the Control Panel's Add/Remove programs dialog. In the Add/Remove Programs dialog on the left-hand side you will see a "View installed updates" link. Click on that and in the new list you will see the Silverlight service release for 11.2.20112.2068 (after it's installed). Select this update and uninstall and you'll go back to the previous version you had.
i have not installed the latest service release. are the easy to roll out of incase some other issue arises from installing it?
You produced this error after installing the latest service release for 11.2 SL4? (11.2.20112.2068)
I've built another sample and I'm trying whatever I can think of to try and reproduce this. I'll get back to you shortly.
stack
i built a new test page in the app, same unable to generate xml error.
see attached