You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using VueyeComponent to display a very paginated large table (with 300,000 rows).
Currently, the excel export button would export rows that are currently displayed:
However, many applications (including ours) require exporting the entire table for further processing.
Displaying the entire 300,000 in a single page can get us by, but most often result in crashing the HTML page.
I would argue that the Excel export button should export all the data passed to the table, or at least there should be a flag to set/control this behavior.
The text was updated successfully, but these errors were encountered:
Agreed, but it hard to define "big". For example, in our case, 300000 is not big enough to crash the app when you create a table in memory that is not going to be displayed (and just exported!) - but forcing 300000 to be displayed before being exported (current code) would definitely crash due to unnecessary rendering. Thus, I think it is a good idea to give developers the agility to configure this behavior.
We are using VueyeComponent to display a very paginated large table (with 300,000 rows).
Currently, the excel export button would export rows that are currently displayed:
However, many applications (including ours) require exporting the entire table for further processing.
Displaying the entire 300,000 in a single page can get us by, but most often result in crashing the HTML page.
I would argue that the Excel export button should export all the data passed to the table, or at least there should be a flag to set/control this behavior.
The text was updated successfully, but these errors were encountered: