I am pretty new to QV but this community has been very helpful. I have two questions I need answers to.
My dataset is pretty huge (18 lakh rows). And, in a straight table I am displaying output based on selections made. This table will have around 15 columns max. I made sure that some selection is made on the sheet so that this object doesn't run out of memory. However, when multiple selections are made (say, Countries 1 2 and 3 are selected together), this table runs out of memory.
Q1: Is there a way to avoid this?
Q2: We are planning to host this using QV publisher license. Since it is on a server there will be higher RAM alloted. So will this object be able to run on the server without losing memory?
Kind of urgent. Please help.
Try to restrict the user to select as much of as selections, may be you are working in your machine with low configuration, if you deploy this in server with huge configuration there you will not get this error.
If the same exists in server also then use
Calculation Condition in General Tab of Chart properties, if you have any ID field then use like this
=Count(ID) < 10000
This will restrict the user to limit the valid records to display in chart by 10000 records, if it displays faster then increase the count.
Hope this helps you.
Exactly as Jagan said. Restrict the table and please notify the end users to apply more filters. Do this in table Properties>General>Error Messages>Calculation condition unfulfilled>Custom Message: ='Please apply more filters. Select less then 10 000 rows. Now are selected: '& num(sum(Row),'# ##0')&' rows.'
Another solution would be move your calculation from Expression directly to loading script.
Memory issues can arise for a number of reasons, including the hardware being used. In my experience, memory problems have usually arisen when the data structure from the script is not quite as anticipated.
It may be worthwhile checking to see whether your script is working excatly as you expect.
I have calculation condition unfulfilled error with this expression : =Count(PostID) < 100.
By the way, inyour expression, if the ID is more than 10000, then it will only consider only the first 10000?
For example, count(ID) = 25000
1. without filter = the straight table will show first 10000 ID
2. With a filter (decrease count(ID) to 15000 = the straight table will still show first 10000 ID
3. With 2nd filter (decrease count(ID) to 9000 = the straight table will show all 9000 ID.
How if i want to show first 1000 with descending date in calculation condition?
I have the same problem in my big data application, the row is in million count, so i face the same issue.