[Filament v2] How to prevent full page re-render (and data re-fetch) when opening a BulkAction confi

[livid marsh]

Hi everyone,

I'm facing a performance issue with Filament v2 (Livewire v2) on a page that contains heavy components

When I use a BulkAction with requiresConfirmation(), clicking the bulk action button triggers a Livewire request to fetch the modal content. This causes the entire page to re-render, re-fetching all the data for my heavy components (Maps, Inputs, etc.), which leads to a significant lag (5-10seconds) before the confirmation modal actually appears.

Does anyone have a workaround or a "best practice" for handling confirmation modals on heavy pages

[stuck fjord]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[wintry marlin]

This is common for Livewire espeically v2. We tend to advise limiting displayed results to 100 max, ideally 25-50. And then anything more that's grander, add a head action instead

[livid marsh]

I updated to v3, but when I open the content modal, the download size is still several MB, equivalent to one page transition of pagination. Is there a way to optimize this since the modal doesn't change the table data?

[lapis tartan]

We introduced a „partial“ concept in v4