I just upgraded to Infragistics 2010 vol 2. Our users use to be able to right click on a web grid, select the Export to Excel menu item and then see the data export to excel.
After the update when I right click on the grid, select export to excel I get the following message in Excel:
This Web query returned no data. To modify the query, click OK, click the name of the external data range in the name box on the formula bar, and then click Edit Query on the External Data toolbar.
The above message is an excel message that wants me to modify the fomula in cell 1A. Cell 1A simply has the text value: ExternalData_1
Anyone have any ideas?
Hello,
For better support, please provide more information to this thread in this particular.
From my understanding you have many options for exporting data to excel such as loading it initially from a DataSet for example which can be the same databinded to the grid. For more information can be reached here: http://help.infragistics.com/Doc/ASPNET/2010.3/CLR4.0/?page=ExcelEngine_Populating_a_Worksheet_from_a_DataSet.html.
Let me know if you have any questions with this matter. Thank you.
Sincerely,Duane HoytDeveloper Support Engineer, MCTSInfragisticshttps://es.infragistics.com/support
Hi, yes I do understand there are different options for exporting data to excel. We do use the infragistics excel export stuff successfully in some of our grids. This is not the problem and we understand the issue after a bit more research on our side.
We have lots of grids where we do not need to hook in full infragistics export support and instead rely on Internet Explorer's native ability to export any html table to excel. If you right click on any html table in IE you will see the "Export to Excel" option on the right click popup. This is where the problem exists.
Older version of the UtraWebGrid generated client side html that was compatible with the native IE export function. The client side html generated by the latest release of the UltraWebGrid does not allow this IE native feature to get at the data.
Is it possible your team will be able to put our a hotfix for this problem?