Previously, the #ExportToExcelButton click handler used to include all page-level filters, but recently i realized that it has only main filter. This results in only the main search term being used for Excel export, and ignores all other applied filters, which breaks the consistency between on-screen data and exported data. Was this change made intentionally? If yes, could you please share the reasoning or benefit behind this design decision?
Also, is there a recommended way to restore the previous functionality where all filters were preserved during Excel export?
$('#ExportToExcelButton').click(function () { _excelColumnSelectionModal.open({ filter: $('#ContentsTableFilter').val() }); }); //Expected $('#ExportToExcelButton').click(function () { _excelColumnSelectionModal.open({ filter: $('#ContentsTableFilter').val(), titleFilter: $('#TitleFilterId').val(), typeFilter: $('#TypeFilterId').val(), textFilter: $('#TextFilterId').val(), isDefaultFilter: $('#IsDefaultFilterId').val(), isPublishedFilter: $('#IsPublishedFilterId').val(), regionNameFilter: $('#RegionNameFilterId').val(), locationNameFilter: $('#LocationNameFilterId').val() }); });
1 Answer(s)
-
0
Hi @sailoper
Thank you for your feedback. We have created an issue regarding this matter, and you can track the progress through that thread.
As you suggested, applying the fix in the described manner should lead to the most optimal resolution of the issue. Specifically, updating the function listening to the ExportToExcelButton click event so that it passes the required arguments when the modal opens would indeed be the correct approach.
Markdown is supportedCopy & paste or drag & drop images (max 30 MB per image)
