I have created a solution in the Caption bar to determine how long it will take to export a table to Excel. I did so, by timing it myself how many records I am sending to Excel, e.g. 100.000 records takes 5 minutes, and 20.000 records take 1 minute. It takes a bit longer when exporting from the web application vs the Enterprise version. The Caption bar now tells me an approximate time it will take to send it to Excel, which is very close to the second, whether it takes 10 seconds or or 10 minutes.
Is it possible to have some kind of Progress bar showing how many estimated minutes/seconds it is left until the export is finished? Qlikview is sort of locked while it is working on exporting to Excel. Not sure whether it is possible to show something else while Qlikview is busy exporting and its memory (Qlikview or my own computer) is tied up.
It has been very useful for me, as sometimes I might accidentally send to Excel before making selections, which can cause the computer to "explode", sort of, or at least take extremely long time before it is ready for the Export. In the case I haven't saved my application recently, I might lose some things I have done, if I don't feel like waiting forever.
The best answer I can provide here is along the lines of the export functionality is somewhat purposefully not all that robust, as QlikView is an analytics tool, not an ETL tool... Many customers try to use us this way, but we are not likely the right product if that is your main use case. What the engineers envision for exports are fairly small files, the default setting in the latest tracks of QlikView limit the server to 3 minutes to export the file, or the export fails, the setting is adjustable, but this sort of drives the point home that we are not really an export tool, or ETL tool to allow for exports to other products etc. Hope this helps a little.
That being said, the one thing you may want to look into if exporting is a large chunk of what you want to do, is the NPrinting product:
That may potentially be a better solution in this use case.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
The best answer I can provide here is along the lines of the export functionality is somewhat purposefully not all that robust, as QlikView is an analytics tool, not an ETL tool... Many customers try to use us this way, but we are not likely the right product if that is your main use case. What the engineers envision for exports are fairly small files, the default setting in the latest tracks of QlikView limit the server to 3 minutes to export the file, or the export fails, the setting is adjustable, but this sort of drives the point home that we are not really an export tool, or ETL tool to allow for exports to other products etc. Hope this helps a little.
That being said, the one thing you may want to look into if exporting is a large chunk of what you want to do, is the NPrinting product:
That may potentially be a better solution in this use case.
Regards, Brett
To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question. I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.
Don't get me wrong. Qlikview is a fantastic tool. I couldn't live without it in my job. Have been working with it for 15 years, and I keep finding new ways every day to make my life easier.
One idea leads to another, and this board has given me so many good ideas.
.png "Former Employee"){kind=icon}
