How to customize route parameters and query conditions under table

[slps970093]

Package

Table builder

Package Version

v3.2

How can we help you?

Suppose my url path is /hello/{id}, but the input form displays no problem, but as soon as I press delete or search, the problem occurs. what do I do?

Pressing delete will not actually delete the data, but the data will still exist in the DB.

I don't want to use the filter method because there is no need to provide filtering and filtering

<?php

namespace App\Filament\Resources\RemoteService\BroadcasterResource\Pages;

use App\Filament\Actions\RemoteService\Quota\ReleaseUserAction;
use App\Filament\Resources\RemoteService\BroadcasterResource;
use Filament\Resources\Pages\Page;
use Filament\Tables\Actions\Action;
use Filament\Tables\Columns\TextColumn;
use Filament\Tables\Concerns\InteractsWithTable;
use Filament\Tables\Contracts\HasTable;
use Filament\Tables\Filters\SelectFilter;
use Filament\Tables\Table;
use Illuminate\Contracts\Support\Htmlable;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\Relations\Relation;
use App\Models\RemoteService\Assign as ModelServiceAssign;
use App\Models\RemoteService\Broadcaster as ModelsBroadcaster;

class AssignUserPage extends Page implements HasTable
{
    // 自定義表格
    // https://filamentphp.com/docs/3.x/tables/adding-a-table-to-a-livewire-component#adding-the-table
    use InteractsWithTable;

    protected static string $resource = BroadcasterResource::class;

    protected static string $view = 'filament.resources.remote-service.broadcaster-resource.pages.assign-user-page';

    public function getTitle(): string|Htmlable
    {
        return '分配人員';
    }

    protected $id = '';
    public function mount(int | string $record): void
    {
        $this->id = $record;
    }
    
    public function table(Table $table): Table
    {
        return $table
            ->query(
                ModelServiceAssign::query()
                    ->where('app_service_type', 'app_service_broadcaster')
                    ->where('aa', $this->id)
            )
            ->columns([
                TextColumn::make('remoteService.name')
                    ->label('服務名稱'),
                TextColumn::make('name')
                    ->searchable()
                    ->label('連線者名稱'),
                TextColumn::make('request_ip')
                    ->label('請求方IP位置'),
                TextColumn::make('expired_at')
                    ->label('到期日'),
                TextColumn::make('created_at')
                    ->label('建立日')
            ])
            ->filters([

            ])
            ->actions([
                ReleaseUserAction::make('release')
            ])
            ->bulkActions([]);
    }
}

[e2d2-dev]

i think you're talkin about related data. if you delete model(42) and a related model has model_id = 42 it won't get nulled.

use a check first if a model exists, before accessing it

if($model->{related}){ }

[slps970093]

No, it is not related data, it is single table data

It’s just that the list page has the where condition, but when it’s time to delete it, it won’t be found.

[e2d2-dev]

where is your DeleteAction?

[slps970093]

I tried to write a minimum viable program. The execution screen is as follows. You can see that if I paginate from 5 items to 20 items, the data will disappear. It will only appear after reorganizing. Then I click Delete and it cannot be deleted.

2025-01-28.14-56-17.mp4

code:

<?php

namespace App\Filament\Resources\Blog\CatalogResource\Pages;

use App\Filament\Resources\Blog\CatalogResource;
use Filament\Actions\DeleteAction;
use Filament\Resources\Pages\Page;
use Filament\Tables\Columns\TextColumn;
use Filament\Tables\Concerns\InteractsWithTable;
use Filament\Tables\Contracts\HasTable;
use Filament\Tables\Table;
use App\Models\Blog\Article as ModelArticle;
use App\Models\Blog\Catalog as ModelCatalog;

class ArticleList extends Page implements HasTable
{
    use InteractsWithTable;
    protected static string $resource = CatalogResource::class;

    protected static string $view = 'filament.resources.blog..catalog-resource.pages.article-list';

    protected string|null $catalogID = null;
    public function mount(string $record)
    {
        $this->catalogID = $record;
    }

    public function table(Table $table): Table
    {
        return $table->query(
            ModelArticle::query()->where('blog_catalog_id', (int) $this->catalogID)
        )
            ->columns([
                TextColumn::make('title')
                    ->label('標題'),
            ])
            ->actions([
                \Filament\Tables\Actions\DeleteAction::make('delete')
            ]);
    }
}

[e2d2-dev]

public function mount(string $record)
{
    $this->catalogID = $record; // can be a string (whole model as json), check what this is and change accordingly
}

public function table(Table $table): Table
{
    return $table->query(
        ModelArticle::query()->where('blog_catalog_id', (int) $this->catalogID) // no need to cast to string in eloquent when number
    )
}

}

empty strings on id's are dangerous, check them first. i would recommend to pull a main query and use modifyQueryUsing().

looks like $this->catalogID is empty or bogus and selects random (all?) stuff

[slps970093]

No. I want this list page to display the conditional content I specified.

Let's say I expected this

select * from article where blog_catalog_id = 5

Then his paging should also bring in what I expected where blog_catalog_id = 5

But if you change modifyQueryUsing() as follows:
As long as the number of pages per page is changed, the condition will no longer exist.

<?php

namespace App\Filament\Resources\Blog\CatalogResource\Pages;

use App\Filament\Resources\Blog\CatalogResource;
use Filament\Actions\DeleteAction;
use Filament\Resources\Pages\Page;
use Filament\Tables\Columns\TextColumn;
use Filament\Tables\Concerns\InteractsWithTable;
use Filament\Tables\Contracts\HasTable;
use Filament\Tables\Table;
use App\Models\Blog\Article as ModelArticle;
use App\Models\Blog\Catalog as ModelCatalog;
use Illuminate\Database\Eloquent\Builder;

class ArticleList extends Page implements HasTable
{
    use InteractsWithTable;
    protected static string $resource = CatalogResource::class;

    protected static string $view = 'filament.resources.blog..catalog-resource.pages.article-list';

    protected string|null $catalogID = null;
    public function mount(string $record)
    {
        $this->catalogID = $record;
    }

    public function table(Table $table): Table
    {
        return $table->query(
                ModelArticle::query()
            )
            ->modifyQueryUsing(function ($query) {
                if (!empty($this->catalogID)) {
                    $query->where('blog_catalog_id', (int) $this->catalogID);
                }
            })
            ->columns([
                TextColumn::make('title')
                    ->label('標題'),
            ])
            ->actions([
                \Filament\Tables\Actions\DeleteAction::make('delete')
            ]);
    }
}