This syntax worked till 1 week ago. From then the job doesn't finish successfully and the error is very vague. In publisher the error is "The Source Document was NOT reloaded successfully". Reload in client also doesn't work
So the question is: the "group by" clause have a row limit on witch it works or a memory limit or something like this?
The easiest approach to finding out what the problem is would be to activate the script log under Settings > Document Properties > General > Generate Logfile. This will create a log of the script execution in the same folder as the QlikView document when reloaded. Fire off a reload and wait for it to fail and check this logfile for further information.
We have noted a problem with Group By when you start getting many rows, though it is just as dependent on the width of your tables. We noticed errors with group by for tables as small as 10M rows and other tables of over 30M rows. Not sure what the problem is, or if it is influenced by hardware. (we have 128 GB server, QV version 8.5).
Another somewhat clunky way to aggregate data using QlikView is to export a pivot table from QlikView as a QVD. This requires about the same amount of resources (it appears), and doesn't seem to fail as often. The challenge is automating the process. I have a QVW with a minimized chart that is called via an ExternalProgramTask in Publisher. Upon opening the QVW (or upon reload) a macro runs which exports the table as a QVD (using ExportEx function). This might not be what you are looking for, though.
