- How do I install advanced-table-export-for-filament in a Laravel app?
- Install it with Composer using composer require occtherapist/advanced-table-export-for-filament, then register the plugin in your Filament PanelProvider. After registration you attach the export header action or the bulk action to each table you want to expose. There are no migrations or data stores to publish, so setup is limited to Composer, plugin registration, and the per-table action configuration.
- Which Filament and Laravel versions does this package support?
- The package targets Filament v4 and v5 on Laravel 11, 12, and 13, which makes it a fit for panels that have already moved past Filament v3. If any panel is still on Filament v3 or Laravel 10, this package is blocked for that panel and you should upgrade first or keep the predecessor package there. Confirm the PHP constraint from the Composer metadata against your runtime images before going further, since a mismatch ends the evaluation cheaply.
- Does it export filtered and sorted table data or only selected rows?
- Both modes are covered. The header action exports the current table query, so active filters, search terms, and sorting are inherited from what the operator sees on screen. The bulk action is for exporting only the rows the user has explicitly selected.
- What export formats does the package support?
- It exports to CSV, XLSX, PDF, JSON, XML, and the clipboard from a single modal or a quick action group. The modal lets the user pick columns before running the export, and PDF exports support portrait or landscape orientation. Note that XLSX, DOCX-oriented word processing, and PDF formats pull in additional libraries or binaries, so the dependency footprint is larger than a CSV-only exporter.
- Which PDF driver should I use with this package?
- The package offers multiple PDF backends: Sidecar, Browsershot, Dompdf, and a null driver. Your choice has real container implications, since headless Chrome based drivers require the browser binary, fonts, and enough memory, and they add cold start latency. Dompdf is lighter to provision but weaker on complex layouts, so benchmark against a representative table before committing.
- How is this different from Filament's native export action or alperenersoy/filament-export?
- Filament's built-in export action is aimed at queued, notification-based exports driven by custom exporter classes, whereas this package focuses on exporting the live table query with an interactive modal and multi-format output. It is positioned as a modern successor to alperenersoy/filament-export, which means the migration path is action-for-action rather than a rewrite. Because the successor has few dependents so far, treat the trust transfer as aspirational and validate parity yourself.
- Can it handle large exports of 10k or 100k rows, and does it queue them?
- The documentation does not state whether exports stream or materialise the full result set in memory, and it does not describe first-class queued export support with jobs, storage, and notifications. Assume exports run as a synchronous HTTP request until the maintainer confirms otherwise, and treat request timeouts and memory limits as live risks. Ask the maintainer directly, then measure the ceiling on your own hardware at 10k and 100k rows.
- Does the export respect column visibility and Filament authorization policies?
- This is not documented, and it matters because an export is a data-exfiltration surface. An action that ignores Filament's column visibility rules or canViewColumn checks can emit fields the operator was never permitted to see. Verify policy handling explicitly in a spike before rolling it out to any panel with sensitive columns.
- How do I migrate from filament-export to this package safely?
- Start by inventorying every table that currently exposes an export and record its format set and column configuration. Port the actions one by one into the new package, then run both behind a per-panel feature flag for a sprint and diff the outputs on a representative table. Column order, formatting, date and timezone handling, and null representation are where successor packages typically diverge, so sign off on parity before retiring the old package.
- Is this package production-ready, and how is it maintained?
- Be cautious: it has a single maintainer, zero dependents on Packagist, and a forward-dated release timestamp that suggests a metadata anomaly worth resolving before you pin a version. It also claims support for very recent Filament v5 and Laravel 13 targets, and untested compatibility claims are a common source of works-in-the-demo failures. Pin an exact version, run a spike against your real tables, and ask about a security disclosure process. The package does ship English and German translations, so localisation is not a blocker.