The business users wants to see most of the fields from the fact table in details table. They want close to 36 fields in the details table.
We have close to 8 million rows in facts.
I have a couple of bar charts ,as a user makes selection on the bar chart the table should should change accordingly.
I tried couple of ways listed below:
1) Tried dumping all the columns in a table box, this resulted in a very wide table box i.e. it does not fit in the screen and table box doesn't let expressions or calculated dims in it. The memory can't handle these many rows
2) I tried using a straight table 4 fields as dims the rest dims as expressions ( in order to be able to scroll I had to add them as an expression) I only see blanks in the expression fields ( In spite of unchecking suppress zeros in presentation tab) .So this approach failed.
Any suggestions, many QV developers would have come across this king of situation, where the business users want a details table ( i.e. all fields) which they would want to export into excel .The downside of this approach is the amount of bandwidth that would be used if lets say 5 uses decide to export 10k rows at one time.
What would be the best way to deal with these kind of scenarios ?
About the #2 - you probably need to check suppress 0's and suppress missing.
In general - ask your users, are they sure they want to see a table with millions or even tens of thousands records? Id doesn't look rational. If they agree on a more reasonable number, use it as calculation condition for the table. Occasionally I used this limit in combination with a variable. That is, there is an input box with a number which is used as calculation condition limit.
The idea here is make the fields a selectable list box so that users need to explicitly ask to view all columns . It can help guide the users to use reports with fewer fields. You can use getselectedcount() on the list box to control a max number of fields on the table as well.
.png "Former Employee"){kind=icon}