Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
bme
Partner - Contributor III
Partner - Contributor III

AJAX send to excel / export displays at text

We just recently upgraded to QV11 SR2 and swiched to the AJAX client from the IE pulgin. We're having a problem with the "send to excel" / "export" functionality. When a data set is large enough that it has to be sent as a csv (over the Excel 65K limit) that file is opened as text by Chrome and Firefox rather than being saved as a file. It seems to work fine in IE8 and IE9 using compatibility mode. It looks like the MIME content type being sent back with the file is "text/plain". I would have expected to see "text/CSV" or even the content disposition to be attachment. Is there any way to modifiy these headers to be more explicit or some other work around?

Labels (1)
6 Replies
phaneendra_kunc
Partner - Specialist III
Partner - Specialist III

Does anyone have solution for this? i have the same problem not sure how to fix this or force the browser to open up in text/excel/csv.

m_woolf
Master II
Master II

When I do Send to Excel in Chrome, it adds the file to my downloads and I have to click the downloaded file to open in Excel.

bme
Partner - Contributor III
Partner - Contributor III
Author

The particular issue I posted this about was accepted as a bug by QlikTech and was fixed in QV 11.2. I just tested in my environment and confirmed that it is now working appropriately.

phaneendra_kunc
Partner - Specialist III
Partner - Specialist III

is it true even if you try to export more than 65536 rows?

bme
Partner - Contributor III
Partner - Contributor III
Author

Yes, I tested it with about 90k rows yesterday evening. We're currently on build 11.20.11922.0

phaneendra_kunc
Partner - Specialist III
Partner - Specialist III

Thanks so much Ben. currently we are on 11 sr2. we are planing to migrate to 11.2 sr5 in next month. i guess that will solve the problem.

thanks again.