acetousk
commented
1 year ago This button could start a job that could be executed asynchronously. The retaining generated files and downloading them if they are there has a problem where if the data has changed, then the download csv button wouldn't download the latest data without some kind of checksum which may take just as long as downloading the whole thing anyways (unless there's a trick for this that I don't know about).
This would probably require some JS client side changes, a trigger as to whether the query needs to be done asynchronously, and using a job to generate the needed file and pass it to the client.
Moqui's table function is still very powerful, just show-csv-button="true" to support downloading forms as CSV. But the problem is that the data volume is slightly larger, and basically this download function cannot be used. (The generation time is relatively long and the performance consumption is also relatively high.) So, if this button is generated asynchronously, and another button is responsible for determining whether there are generated files, download them if there are, would it be more suitable for scenarios with large data volumes?