Since ODS generation can cause issues (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23685), and Excel generation is not currently possible, why not using libraries such as https://sheetjs.com/ (and other tools like https://www.papaparse.com/ or web workers for big files?) to convert the generated CSV to Excel or ODS in the browser ? It could be used for reports but also other CSV generated by Koha. We will try this approach in my library, as a local customization.
Maybe this isn't the place (and I would be happy to take this elsewhere) but WHY is it "currently not possible" to get Excel files from reports? Basically any table in Koha has 4 export options: Excel, CSV, Copy, Print. It's a little odd to not also see the Excel option when trying to download a report result. This bug is addressing a gap in Koha that I would like to better understand why the gap exists, but if this is the best way to resolve the missing format, then I will follow this bug with interest!
I believe the perl libraries for exporting in Excel format are very old and could cause memory issues. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23685#c7
(In reply to trevor.diamond from comment #1) > but WHY is it "currently not possible" to get Excel files from reports? > Basically any table in Koha has 4 export options: Excel, CSV, Copy, Print. Just to clarify a little about why these things are different: tables which offer the Excel, CSV, etc. option are controlled by a third-party JavaScript library (DataTables) which includes this functionality. Saved SQL report results don't use the DataTables plugin because such reports could have thousands of results, and parsing that amount of data client-side with the DataTable plugin could crash the browser. Saved SQL report results are instead processed by Perl scripts in order to produce the requested file format for download. For this we depend on a third-party Perl library.
Thanks for providing this context, yall!