[4.x] Using `modifyQueryUsing` to join tables can mess up the table list display.

[bzy107]

Package

filament/filament

Package Version

v4.0.0-beta25

Laravel Version

v12.22.1

Livewire Version

v3.6.4

PHP Version

8.4.10

Problem description

After upgrading to Filament v4, I noticed that the table list displayed with modifyQueryUsing didn't match the data from the actual SQL query. Reverting to v3 fixed the issue, so it seems to be a unique problem with v4.

sql:

select
    *
from
    `owners`
    inner join `patients` on `owners`.`id` = `patients`.`owner_id`
    inner join `breeds` on `patients`.`breed_id` = `breeds`.`id`
    inner join `vaccines` on `patients`.`vaccine_id` = `vaccines`.`id`
where
    `patients`.`registered_at` = '2025-08-11'
    and `owners`.`deleted_at` is null
order by
    `owners`.`id` asc
limit
    10 offset 0

v3:

v4:

However, I found a solution: specifying select fixed the display.

                    ->select([
                            'owners.id',
                            'owners.email',
                            'owners.phone',
                            'owners.owner_name',
                            'patients.patient_name',
                            'patients.type',
                            'patients.registered_at',
                            'breeds.breed_name',
                            'vaccines.vaccine_name',
                    ])

Expected behavior

Displays the same as v3.

Steps to reproduce

1. Run the seeder in the repository. php artisan migrate:fresh --seed
2. Log in using the credentials (test@test.com: test).
3. Navigate to /admin/owners to display the OwnersResource.
   (You can compare this with v3 by switching to the v3 branch and running composer install to downgrade.)

Reproduction repository (issue will be closed if this is not valid)

https://github.com/bzy107/filament_v4

Relevant log output

[rohanAdhikari1]

@bzy107 I might be wrong, but this doesn’t seem to be a bug in Filament. Your query result contains four id fields, and the last one is being assigned to the id attribute in the model result.

As shown in your query output::-

And when debugging inside ->modifyQueryUsing() function with:

dd($query->get()->toArray())

The collection output is:

Here you can clearly see the ambiguous id fields. Since Eloquent assigns attributes based on the last occurrence, the final id value in the query result is being used as the model’s id attribute. This causes the data to appear incorrect in the Filament table.

Fix: To avoid this, you can alias your columns or simply select the required columns in the query, for example:

$query->join('patients', 'owners.id', '=', 'patients.owner_id')
    ->join('breeds', 'patients.breed_id', '=', 'breeds.id')
    ->join('vaccines', 'patients.vaccine_id', '=', 'vaccines.id')
    ->where('patients.registered_at', $maxDate)
    ->select([
           'owners.id',
           'owners.owner_name',
           'owners.phone',
           'owners.email',
           'patients.id as patient_id',
           'patients.patient_name',
           'patients.registered_at',
           'patients.type',
           'breeds.id as breed_id',
           'breeds.breed_name',
           'vaccines.id as vaccine_id',
           'vaccines.vaccine_name',
      ]);

[bzy107]

the last one is being assigned to the id attribute in the model result.

I understand that, but I'm reported this as a bug because I'm unable to retrieve items like the email field, which were displayed correctly in v3. I also added an ID column just in case, but it's also displaying the ID of the last table, just as it did in v3.

v3:

v4:

[Estigy]

Maybe the V3 code internally added something like ->select([model].*) which made sure that all the fields of the model were selected, and this line was then omitted in V4?
That would explain why in V3 the correct fields were taken from the data set...

[bzy107]

Maybe the V3 code internally added something like ->select([model].*) which made sure that all the fields of the model were selected, and this line was then omitted in V4?

That's incorrect. The result of dd($query->get()->toArray()); is identical. The SQL is also identical. It seems the display logic has been modified, but I haven't been able to find it.