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
If there are multiple tables on same page with export, each adding own DataTableExporterEvents::PRE_RESPONSE event listener, exporting any of the tables, fires all registered DataTableExporterEvents::PRE_RESPONSE events. The export file name is overwriten by each event.
As a result every export file is named by last fired event.
If there are multiple tables on same page with export, each adding own DataTableExporterEvents::PRE_RESPONSE event listener, exporting any of the tables, fires all registered DataTableExporterEvents::PRE_RESPONSE events. The export file name is overwriten by each event.
As a result every export file is named by last fired event.
expected output
export from
table1
named astable-1-export.xlsx
export from
table2
named astable-2-export.xlsx
current output
export from
table1
named astable-2-export.xlsx
export from
table2
named astable-2-export.xlsx
DataTableExporterResponseEvent should contain instance of DataTable, so we can decide inside event callback to skip it if it belongs to other table.
Or fix DataTableExporterManager to dispatch only events that belong to exported DataTable.
The text was updated successfully, but these errors were encountered: