Filament•2y ago

Save MM relationship with single select

Hi, I have a condition in my form that checks if a user has only permission to one "location" and if so, the select multiple should render as single select where the single location value is already selected. This is easy by just querying for one location and set it as default. But because the data structure expects a many to many relation I need to modify the save method to attach one single location to the MM table. I tried it like this, but that doesn't work:

            return Forms\Components\Select::make('locations')
                ->label(trans('locations.singular'))
                ->disabled()
                ->options(Auth::user()->locations()->get()->pluck('name', 'id'))
                ->saveRelationshipsUsing(fn($data, $record) => $record->locations()->sync($data['locations']))
                ->disablePlaceholderSelection();

            return Forms\Components\Select::make('locations')
                ->label(trans('locations.singular'))
                ->disabled()
                ->options(Auth::user()->locations()->get()->pluck('name', 'id'))
                ->saveRelationshipsUsing(fn($data, $record) => $record->locations()->sync($data['locations']))
                ->disablePlaceholderSelection();

How should the code look like? Thank you!

19 Replies

ProdexOP•2y ago

I somehow need to access the value of locations, but $data isn't available in the closure

Lind•2y ago

I think $state should be available

ProdexOP•2y ago

hm... $state returns null actually I think it's because at this point the record has already been created, but without the relationship

Lind•2y ago

I'm not that familiar with this use case sadly, where i use it i have $state available. Hopefully someone with better understanding of it can help 🙂

Patrick Boivin•2y ago

@prodex Haven't tested but I think $get might work in this context:

->saveRelationshipsUsing(fn($get, $record) => $record->locations()->sync($get('locations')))

->saveRelationshipsUsing(fn($get, $record) => $record->locations()->sync($get('locations')))

ProdexOP•2y ago

even get('locations') returns null 🙈

Patrick Boivin•2y ago

Is the locations field a relationship on the resource model?

ProdexOP•2y ago

yes, it's a mm relation on the model, but I can't use relationship() because it cannot create the relation correctly as it expects a m to 1 relation.

Patrick Boivin•2y ago

I see! Had the same problem recently. You need a pivot model. Have a look at this thread, maybe it can give you an idea : https://discord.com/channels/883083792112300104/1116402597335674950/1116412576067240099

ProdexOP•2y ago

hm... it seems like filament expects a belongsToMany method, but if I'm using it like so I'm getting "Call to undefined method Illuminate\Database\Eloquent\Relations\BelongsToMany::getOwnerKeyName()"

            return Forms\Components\Select::make('locations')
                ->label(trans('locations.singular'))
                ->disabled()
                ->relationship('locations', 'name', function (Builder $query) {
                        return $query->whereHas('users',
                            fn (Builder $query) => $query->where('user_id', Auth::id()));
                })
                ->disablePlaceholderSelection();

            return Forms\Components\Select::make('locations')
                ->label(trans('locations.singular'))
                ->disabled()
                ->relationship('locations', 'name', function (Builder $query) {
                        return $query->whereHas('users',
                            fn (Builder $query) => $query->where('user_id', Auth::id()));
                })
                ->disablePlaceholderSelection();

it works with ->multiple() though

Patrick Boivin•2y ago

If your relationship is a BelongsToMany, Filament will try to create the end model (not what you want). If you instead rewrite your relationship as 2 HasMany with a pivot model (e.g. Thing -> ThingLocation <- Location), the repeater will correctly attach to the ThingLocation, instead of trying to create a Location. Hope that makes sense 😄

ProdexOP•2y ago

yes I read that, but using hasMany throws another exception where it says "belongsToMany" is expected instead of "hasMany" so it's already the correct expected method. I'm just not sure what the "getOwnerKeyName()" exception wants to tell me.

Patrick Boivin•2y ago

Did you update the relationship on your resource model? (i.e. point to ThingLocation instead of Location)

ProdexOP•2y ago

yes I added this method to the model and tried using it:

    public function IncidentLocations()
    {
        return $this->hasMany(Location::class);
    }

    public function IncidentLocations()
    {
        return $this->hasMany(Location::class);
    }

But that results in the exception where it says "belongsToMany" is expected instead of "hasMany"

Patrick Boivin•2y ago

If you introduce a pivot model, your relationship should look like ->hasMany(IncidentLocation::class) and the repeater should write to incidentLocations instead of locations Maybe I'm missing something? Sorry if I'm confusion you more than helping you 🥴

ProdexOP•2y ago

okay, but if it already breaks because of the wrong method name (hasMany), then it shouldn't matter whats inside the method params.

Patrick Boivin•2y ago

Forms\Components\Select::make('incident_locations')

ProdexOP•2y ago

hm okay, it still throws the same exception. Isn't there a way to hook into the relation process and attach that single relation? It seems a bit weird right now. it's all I want 😂 my solution now: call the select field "location" (singular), save the id to the create class as attribute (if it exists) and then attach the relation manually within the afterCreate() hook.

Patrick Boivin•2y ago

Yeah, that's a more manual approach but it works fine, that's what I was using at the start of my little experiment. There's surely a way to make it work for your use-case without the custom code but it's hard to debug remotely.

Gaming

Programming

Save MM relationship with single select