Export Ignores Applied Filters and Scans Entire Table #1887
Unanswered
umar-zealtouch
asked this question in
Q&A
Replies: 3 comments 33 replies
-
I believe this should be a top priority since the export feature currently fails to include the desired filtered results. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Had the same issue.. I fixed it by writing my own export which aswell, handles the filters.. I could also not find any fixes for the problem with the inbuilt export |
Beta Was this translation helpful? Give feedback.
21 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am experiencing an issue with the export functionality where applied filters (from query string livewire component params or otherwise) are not respected during data export. While the page correctly shows filtered records, exporting those records results in the full dataset being scanned, causing performance issues.
✅ Expected Behavior:
When filters are applied (e.g., filtering transactions by user_id), the export should only include and query the filtered records. For example:
❌ Current Behavior:
Even when filters are applied, exporting records triggers a full table scan. It applies the record limit correctly (e.g., exports 100 rows), but the query does not include the filters, so it's essentially scanning all 1000 rows and then slicing the result. As a result we never get the actual results that were in the filtered table.
This results in extremely slow exports for large datasets, even though only a small portion of data is visible/filtered.
🧪 Reproduction Steps:
Beta Was this translation helpful? Give feedback.
All reactions