Hi,
I tried to simple copy and paste your sample about Client side Excel library overview on a local environment.
I did different tests:
When I click on the export button and the whole procedure starts I always get the same error you can see here: Error. It is related to an uncaught error in infragistics.xml.js...
But, why is it strange? Because if I reclick, the whole procedure does not return that error again. So, I try to debug a little and I found the following line:
var workbook = new $.ig.excel.Workbook($.ig.excel.WorkbookFormat.excel97To2003);
to be the reason of this error.$.ig.excel.WorkbookFormat.excel97To2003 is right (I can see it is a sort of enumerable property, and also changing it, it is always correctly found.The new $.ig.excel.Workbook(...) generates the error I described.Working wiht Google Chrome developer tools console, I was able to see that:
Hello Flavio,
Thank you for contacting Infragistics!
I have done some looking into this matter and have the following information. First I would like to note that the client side excel export is still in CTP and therefore not recommended or supported to be used in production environment. So far I have been unable to reproduce the issue you are using. I am attaching my sample please let me know what behavior you see when you run the sample. I also have the following questions:
What browser or browsers are you using? What service release are you using for v14.2?
Hi Mike,
service release is 14.2.2140. Actual browser is Google Chrome.
As I said you in other post (Error xporting: JSZip is not defined) this error is not occurring with the sample you provided me.
Now I will try to extend it with the sample there is on the web site.
Thanks in advance
Flavio M.
yes, still getting same error.
Clicking export on your web sample it works, but copying and paste all the code into my projet gives me that error.
As I said you I use Google Chrome browser, but same thing happens also with Internet Explorer and Mozilla Firefox. I just copied all code I found into the sample, including Blob and FileSaver libraries. I asked to do a test also to a collegue of mine and, copying that on his local web page, he was able to reproduce the same issue.
Anyway, at the moment it is not so urgency. It seems I am the only one having this problem and, thanks to your suggestions about alpha/beta release, I don't think I will choose to put this feature on production environment. I will continue to use the IG server side Excel export, that I already used and it worked great.
Thanks for the moment
FM
Is it possible that when copied the code from the sample to your own page you missed a script or something like that to be included? When I run the sample you linked to previously I am able to export without any issues. What browser are you using? Are you still getting the same error?
at the moment I am not able to provide you an isolated sample.Copying and paste web sample should be enough, but the difference between web sample (error appears) and yours (no error) leave me a little confused.
I will try to do more tests on it. Even if I am a little scared to put it on production, if it is still an alpha or beta feature...
Thanks for the moment.
Thank you for the update. Can you provide me with an isolated sample that reproduces the behavior you are seeing? This way I can investigate this matter to see what may be causing the behavior you are seeing?
Please let me know if you have any questions concerning this matter.