Hi Aaron,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

Sorry to disappoint you, but at this time, we don't have any built-in solution to achieve this

You can suggest it to our developers, though - they will do their best to make a solution in the future.

Please feel free to search on our suggestions page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

If you have coding skills and wish to try to make a custom solution now,

you can check out our available hooks for Developers on this documentation and see if you can find any hook that might help.

Please be advised that custom solutions with hooks are not included in our support.

You can also research resources such as Stack Overflow to see if any other user perhaps found a workaround.

( We do like to give examples for certain solutions, but for this use-case, we, unfortunately, don't have anything yet)

Hi Aaron,

You're welcome, I am happy to advise.

At the moment, there could be only some workarounds, I am not sure if this will help, but this is how the number of exported rows is currently working via Table Tools :

The table tools functionalities are based on a 3rd party HTML5 library and they are not customizable. Unfortunately, the library allows very little “fine-tuning” of the generated files, so font, size, and other properties cannot be changed.

There are some limitations in this library we will emphasize for your awareness:

• For tables with server-side processing, only the visible rows will be exported to any format.
  If you want the entire table to be exported (or copied to a clipboard), you need to choose the “Show All” feature in the “show … entries” block, and then do the export:
• Generated PDF, XLS, CSV are not customizable. Unfortunately, the library allows very little “fine-tuning” of the generated files, so font, size, and other properties cannot be changed (but the title can – see below).
• Conditional formatting is not reflected in any of generated export files.
• Other front-end extensions cannot be combined with Table Tools. If you have row grouping enabled for the table, or there are some customizations you did yourself, they won’t be reflected in the generated Excel, CSV or PDF document, nor in the clipboard.
• When you export tables with the wpDataTables plugin, please note that you can export values, but not formulas. WpDataTables doesn’t support exporting formulas, so a Formula column will be exported only with values; and any calculations of Average, MIN, MAX, and Total will not be exported at all.
• Exporting images is not possible at the moment, but you are able to export them as HTML with the new “Include HTML” option.
• You can’t export columns that are hidden – they will not be visible in any exporting or printing tool.
• Export numbers with comma as decimal separators have issues in the Excel report. Please use the CSV export button or change column type to string for these columns.

-

If you wish to try better PDF export features, our advice would be to acquire something similar to the WP Advanced PDF plugin, which offers a lot more options when creating PDF files from our tables, along with other content on your website.

This is the current logic and the limitations for the Export tools.

So for example, if you have a table that has our server-side processing enabled on it;

and if you activate pagination in the Table - then only the rows from the 'visible page' are going to be exported.

Manual Tables always have server-side processing in the 'background', while for SQL Query based tables, you have the option to toggle server-side.

We also added the ' Custom rows per page' in the Table display settings, so you can determine how many rows they can see in each table page, etc.

You could also use filtering to load only some specific filtered data, and so on...

I hope that could help as an idea of the possible workarounds.