Clicking on the last page/record returns an error attached.

@vinitl Great, the code snippet uploaded by you suggests that you aren't using any special approach to query (more than 10000 or resources.appian.analytics.application.maxreportrows/number of analytics engines records), which is infact needed. To the best of my knowledge, this could be a cause of the error, because the moment the expression evaluation see the 10001st record, it starts throwing an error.

The approach we adapted for trespassing this limit is, we created a separate report(which is same as the original report we should query using a!queryProcessAnalytics()) and grouped the records by year, month and day. By this we obtain a unique combination of year, month and day and a count of rows against each combination. On the each combination obtained, you can apply the a!queryProcessAnalytics() iteratively (where the year, month and day will act as filters) on the report which is actually intended for querying and merging the datasubsets of all combinations will lead to a resultant datasubset. In this approach, in the worst case scenario you will be able to handle even 10000 records a day. I wouldn't say that this is the best approach, but I think that even the alternative approach will be more or less the same.

I agree that the iterative approach calls a!queryProcessAnalytics() multiple times creates burden on the system, but it is inevitable because of the limitation that expression evaluation results in an error after seeing (10000 or resources.appian.analytics.application.maxreportrows/number of analytics engines records)+1st record.

Also if possible, please do take a look at /search?q=OriginalPostID-144871 which elaborates the approach further. And let's see if any other Appian practitioners comes up with a better approach.

Please do let me know if you have any follow-up questions.

@vinitl Great, the code snippet uploaded by you suggests that you aren't using any special approach to query (more than 10000 or resources.appian.analytics.application.maxreportrows/number of analytics engines records), which is infact needed. To the best of my knowledge, this could be a cause of the error, because the moment the expression evaluation see the 10001st record, it starts throwing an error.

The approach we adapted for trespassing this limit is, we created a separate report(which is same as the original report we should query using a!queryProcessAnalytics()) and grouped the records by year, month and day. By this we obtain a unique combination of year, month and day and a count of rows against each combination. On the each combination obtained, you can apply the a!queryProcessAnalytics() iteratively (where the year, month and day will act as filters) on the report which is actually intended for querying and merging the datasubsets of all combinations will lead to a resultant datasubset. In this approach, in the worst case scenario you will be able to handle even 10000 records a day. I wouldn't say that this is the best approach, but I think that even the alternative approach will be more or less the same.

I agree that the iterative approach calls a!queryProcessAnalytics() multiple times creates burden on the system, but it is inevitable because of the limitation that expression evaluation results in an error after seeing (10000 or resources.appian.analytics.application.maxreportrows/number of analytics engines records)+1st record.

Also if possible, please do take a look at /search?q=OriginalPostID-144871 which elaborates the approach further. And let's see if any other Appian practitioners comes up with a better approach.

Please do let me know if you have any follow-up questions.