Hello.
I'm using IgniteUI grid. Its datasource is a JSON object obtanied via AJAX. The grid is locally paged and filtered. I need to export the entire set of results (using filters applied but without mattering the paging).
I've seen Ingragistics Excel overview but it doesn't use the filter. Even if I could add filter parameters, I would have to get the data from the DB again, and I'd like to avoid that.
I've also seen Client Side Excel Library but I couldn't get it working. Also, I need to support IE9+, and that solution is not IE9 compatible. It could be make IE9 compatible posting the data to the server, and genereting the file to download from the server, however I also read that: "the client side excel export is still in CTP and therefore not recommended or supported to be used in production environment" in this post.
So, how can I do to export the grid? Maybe somehow serializing its information and posting it to the server?
Thanks,
Diego
Hello intecomp,
I assume that the following forum thread could be useful for you: https://www.infragistics.com/community/forums/f/ignite-ui-for-javascript/72024/how-to-export-the-current-displayed-iggrid-data-i-g-after-sorting-or-filtering-to-excel
If you need further assistance, please let me know.
Regards,
Tsanna
Can I help you with anything else?
The exportation is closed, the link you gave me was all I needed.
I'm having a little trouble now with a different issue. If I start the grid with records and then delete everyone of them, I see the grid with 0 records. However if I want to start the grid without any records, nothing shows. Is this a functionality or an issue? How can I get the empty grid form the begining?
What do you mean by "nothing shows"? Does the grid at least render its headers? I tested similar scenario on my side and both ways that you mention, the grid retains only headers. Which version are you using?
Waiting for your reply.
Hello Tsanna.
I mean that not even the headers. Absolutely nothing. In fact the <table> element I use to build the grid disappears. I'm using v14.2.20142. Maybe this could be a scenario issue.