Paginated report fails when too large

[joelchampagne]

We have an example of a paginated report that will fail when run for a year's worth of data but not for a quarter's worth.

This admittedly is about 66,000 rows of data (and maybe 30 columns), but audit requirements dictate a YTD version of the report.

The query performance is not an issue: YTD query comes back in seconds, but rendering "dies" with an error, after sitting on "Loading Report..." (with the spinner) for several minutes: An unexpected error occurred.

My thinking is we can build a version of the report which is a raw extract that is CSV and delivered via email - not through Power BI, though. Other ideas? Seems like there's a resource limitation? We're using Premium (P1).

[GilbertQ]

Hi @joelchampagne 

It does appear to be a limitation in terms of the amount of data returned in the report. What happens if you had to try and run the report on a schedule with a CSV attachment?

[joelchampagne]

Tried to schedule and deliver it that way, did not see anything come out of the service, as an email.

We're trying to experiment now - e.g. filtered to a subset of data that was still a lot, and it rendered ok... is it possibly something in the data itself? maybe: we're following that angle, too.

[GilbertQ]

Yeah there could be some backend limitations!