Hi @DanHarrin.

So Custom Columns are mostly for rendering static (read-only) information, or with a little bit of Alpine magic can be used to update the information of the record.

But how about rendering a custom Livewire component? Yes, in the table cell. Fast-forward, i was actually able to make it work. And the component does its job well. But there's a bug. Whenever i sort the table by any other column, or do filtering - everything breaks.

Uncaught Snapshot missing on Livewire component with id: e7WMBVwOqIuTm6OiWZap

Table Pagination, though, doesn't cause the bug to happen. I tried to set the 'key' for my component, but no luck.

// resources/views/tables/columns/my-custom-column.blade.php:

<div>
    @livewire(\App\Livewire\MyCustomComponent::class, [
        'model_id' => $getRecord()->id
    ], key('anchorKey-'.$getRecord()->id))
</div>

I imagine that a Filament Table is basically a Livewire component by its own, and my component becomes the nested one.
Tried to mark model_id in MyCustomComponent as Reactive:

#[Reactive]
public int $model_id;

didn't work.

Is it actually possible to implement and i simply missing something? Or i should better re-imagine the approach and try something else?

Just for a context: my livewire component checks for a certain value in the database. If it exists - it just displays it. If not - the button shows up, by pressing which - it triggers a Batch of Queued Jobs. The component displays the progress of the batch in the cell, an when finishes - pops up a Filament Notification, gets the value from the database and diplays it in the cell.

Build a Custom Table Column