I have run into a situation with a customer where she needed to export the datasets from four large (in excess of 25 Mb) reports, but was unable to access the entire report due to current UI limitations. The resultant CSV's were larger than could be sent via Gmail. In the end, we were able to rebuild these reports as single query bionic rules and utilize the "export to S3" functionality on the Rules engine to provide the customer these results. 



While this is a viable work around, and a great way to access the entirety of your large report datasets, it seems like extra work to rebuild something that is already build in another module. Would Product consider adding the current "export to S3" piece to Report Builder? I think the current functionality would be helpful, but have additional suggestion:

• In Report preview - give the size of the total dataset (both physical size and # of rows) - this could guide users into which export method would work best for them.

Any feedback on this would be greatly appreciated.