-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work for large datasets #3
Comments
This extension transform the Qlik tables to HTML code in order to show the whole look&feel when exporting to Excel or Word. So it does not work with the hipercube of data, but the rendered elements. Because of that every row and column needs to be shown in the screen before exporting, if not the html code created on the fly won't contain the hidden rows. Qlik just shows a few number of rows and then it offers the button 'Show more'. To prevent that the extension put the html table in a large iframe (previous to export) that allows to contain all the rows or a significant number of them. The iframe size is width: 20000px;height: 50000px. If you need to show more rows or columns you'll need to enlarge it. Anyway I can asure you'll always be able to show the 100% of the rows from a large table, it's thought to print smart datasets, as the large ones are more supposed to be used as datasource rather than a nice table for presentations Regards. |
I get a message that the cube is too large. As I understand it should be possible to export large datasets. I read in this treads previous post that I have to change the iframe size. Does that solve the cube problem? And if so how do I change the iframe size exactly? I haven't found the settings where I can change the iframe. |
I kind of have the same question as Jeffrey |
If the export data type is changed from a blob to a stream, it should be possible to export much larger datasets and avoid using Hypercube paging. |
I tried using it with large data sets, but not large enough to challenge the blob size. It works correctly till 1725 rows
The text was updated successfully, but these errors were encountered: