Qlik Sense - Straight Table - 220 columns - error

[AnupK]

Hi,

I am working on a Qlik Sense report which requires 220 columns to be made available in a straight table. The end users want to be able to download the data from the table in excel  for reference. 

However, when I go beyond 150 columns I am getting a "Calculation timed out" error when loading the table. I checked the Qlik Sense server memory; it peaks to 40 GB but is nowhere close to maximum limit of 120 GB. So, lack of memory is not the issue. 

There are several dimension tables in data model from which columns are being used in the straight table. 

What could possibly be the reason for this? Are there any limitations on the number of columns in straight table?

Request help as I have been trying to find a solution to this for several days. 

Regards

Anup

[skamath1 · Accepted solution]

That is too much to show in the straight table.

You can save the data to CSV file with the store command at the end of the script

https://help.qlik.com/en-US/sense/November2018/Subsystems/Hub/Content/Sense_Hub/Scripting/ScriptRegu...

[AnupK]

Is there no way I can have those columns in the straight table?

[rbartley]

Thinking about it from a practical point of view, how useful will a spreadsheet be with 220 columns?  This would involve a lot of scrolling for the end user.  Couldn't the data be broken down into different files reflecting different needs?

[marcus_sommer · Accepted solution]

Qlik and also no other BI tool is designed for such a task because it doesn't make much sense neither in regard to visualize the data nor to transfer the data from one tool into another at least not with the detour over the UI.

The best option to provide such large tables is to create them within the script and to store them within a (public) storage.

- Marcus

[AnupK]

@rbartley - Unfortunately the users also want the entire data dump from the table so that they can run some adhoc analysis on the data at their end. 

@skamath1 and @marcus_sommer  - I guess as mentioned , the best solution would be to combine the entire data model into one table along with the calculated dimensions and measures used at the sheet level and run a store command to save the data in csv. 

 Alternatively, will also run a check to see if N-Printing can be of any help to transfer the data directly from the straight table (the one that is not getting loaded currently) . This, if worked, might save me the effort of combining the entire model into one table. 

Thanks everyone !

Anup