Given there are api / operational limit in BCs cloud for larger customers that plan on using open/edit in excel feature on large datasets they may not be aware that it could impact performance.

An example recently where a user wanted to export data from the CF availability by periods window - which is bound to the virtual date table - the open in excel would not work because it was trying to export millions of date rows due to a lack of filtering. A simple check (countapprox) prior to initiating this function could alter the user that the number of rows to exported is high (against a threshold) and that it might take time and then maybe send that request to job queue/background, or they can cancel set a filter and try again. This would avoid users starting at a working...dialog.