F
Filament•4mo ago
Lars van Herwijnen

Update hidden fields (Relationship)

So I have a select input that is a relation. This field is hidden or shown based on the type of the user. But when type is changed to Customer the relation, the select, should be updated. I know that the field is not being updated because it is hidden. Is their away around this? 
        return $form
            ->schema([
                Forms\Components\Group::make()->schema([
                    Forms\Components\Section::make()->schema([
                        Forms\Components\TextInput::make('name')
                            ->label('Name')
                            ->required()
                            ->placeholder('John Doe')
                            ->maxLength(255)
                            ->columns(2),
                        Forms\Components\TextInput::make('email')
                            ->label('Email')
                            ->required()
                            ->columns(2),
                        Forms\Components\Select::make('type')
                            ->label('Type')
                            ->options(UserRoles::toArray())
                            ->afterStateUpdated(function (Get $get, Set $set) {
                                if ($get('type') == UserRoles::CUSTOMER->value) {
                                    $set('groups', null);
                                }

                            })
                            ->live()
                            ->required(),
                        Forms\Components\Select::make('groups')
                            ->relationship('groups')
                            ->label('Groups')
                            ->options(Group::all()->pluck('name', 'id'))
                            ->multiple()
                            ->required()
                            ->hidden(fn(Get $get) => $get('type') == UserRoles::CUSTOMER->value),
                    ])->columns(2),
                ])->columnSpanFull(),
            ]);
    
        return $form
            ->schema([
                Forms\Components\Group::make()->schema([
                    Forms\Components\Section::make()->schema([
                        Forms\Components\TextInput::make('name')
                            ->label('Name')
                            ->required()
                            ->placeholder('John Doe')
                            ->maxLength(255)
                            ->columns(2),
                        Forms\Components\TextInput::make('email')
                            ->label('Email')
                            ->required()
                            ->columns(2),
                        Forms\Components\Select::make('type')
                            ->label('Type')
                            ->options(UserRoles::toArray())
                            ->afterStateUpdated(function (Get $get, Set $set) {
                                if ($get('type') == UserRoles::CUSTOMER->value) {
                                    $set('groups', null);
                                }

                            })
                            ->live()
                            ->required(),
                        Forms\Components\Select::make('groups')
                            ->relationship('groups')
                            ->label('Groups')
                            ->options(Group::all()->pluck('name', 'id'))
                            ->multiple()
                            ->required()
                            ->hidden(fn(Get $get) => $get('type') == UserRoles::CUSTOMER->value),
                    ])->columns(2),
                ])->columnSpanFull(),
            ]);
9 Replies
Dennis Koch
Dennis Koch•4mo ago
Hm, I would expect this to work. So the data should save when the select is visible? 🤔
Lars van Herwijnen
Lars van Herwijnen•4mo ago
It should always save, regardless of the visibility of the select. Since if the type changes from e.g. admin, teamlead to customer. The record in the pivot should be deleted. Because a customer type cannot be associated with groups.
Dennis Koch
Dennis Koch•4mo ago
Can you try ->dehydrated(true) after the hidden method. Maybe that's already enough.
Lars van Herwijnen
Lars van Herwijnen•4mo ago
Sadly, that doesn't work. After saving the data is still present in the database. Because I changed the type from Teamlead to Customer i expect this table to be empty.
No description
CT
CT•4mo ago
Funny timing, I just had a very similar issue I solved yesterday. Basically hidden or non-visible fields are not updated (even if you manually update the values with for example using $set and/or using ->dehydrated()). I solved my issue by doing this; 
->actions([
                Tables\Actions\EditAction::make()
                    ->using(function (Project $project, array $data): Model {

                        // Since filament does not update hidden fields we need to first set these to null
                        $project->seo_monthly_budget_eur = null;
                        $project->seo_starts_at = null;
                        $project->seo_ends_at = null;

                        // Since filament does not update hidden fields we need to first set these to null
                        $project->sea_monthly_budget_eur = null;
                        $project->sea_starts_at = null;
                        $project->sea_ends_at = null;

                        // Since filament does not update hidden fields we need to first set these to null
                        $project->sma_monthly_budget_eur = null;
                        $project->sma_starts_at = null;
                        $project->sma_ends_at = null;

                        // and now we override them with the actual values
                        $project->update($data);

                        return $project;
                    }),
            ])
->actions([
                Tables\Actions\EditAction::make()
                    ->using(function (Project $project, array $data): Model {

                        // Since filament does not update hidden fields we need to first set these to null
                        $project->seo_monthly_budget_eur = null;
                        $project->seo_starts_at = null;
                        $project->seo_ends_at = null;

                        // Since filament does not update hidden fields we need to first set these to null
                        $project->sea_monthly_budget_eur = null;
                        $project->sea_starts_at = null;
                        $project->sea_ends_at = null;

                        // Since filament does not update hidden fields we need to first set these to null
                        $project->sma_monthly_budget_eur = null;
                        $project->sma_starts_at = null;
                        $project->sma_ends_at = null;

                        // and now we override them with the actual values
                        $project->update($data);

                        return $project;
                    }),
            ])
I'm happy to submit a PR later to the docs but I'm not even sure if this is expected behaviour or not? Is it supposed to work when using ->dehydrated(true) @Dennis Koch ? Actually, aren't all fields ->dehydrated(true) by default? There is also a ->dehydratedWhenHidden() method which I played with but was unable to get working, same behaviour
Dennis Koch
Dennis Koch•4mo ago
Hm, so I guess that $set() is not working when fields are hidden and not the saving? I am not really sure about this one
CT
CT•4mo ago
$set() itself "works", as in I could change the value to null, then verify and get back the same null using $get() but it simply doesn't save to the database, it would always skip any hidden fields if you get what I mean? so it was pretty confusing for me to figure out what was going on, but I am also only using filament for a couple weeks now so still quite new
Dennis Koch
Dennis Koch•4mo ago
Hm, sounds weird if you are using ->dehydratedWhenHidden(). But I have never used it, so I can't say much about it
Blackpig
Blackpig•4mo ago
I had something similar when I wanted to manipulate the value of hidden field ended removing the hidden field and adding logic to https://filamentphp.com/docs/3.x/panels/resources/editing-records#customizing-data-before-saving
Editing records - Panel Builder - Filament
Want results from more Discord servers?
Add your server
More Posts
Modify Label Options in RelationManager attach actionHello I'm trying to modify the options in attach action form inside a Relation Manager without succField not updating in database, but shows successful updateWhy wouldn't this field be getting updated in the database? ``` public function form(Form $form)Prohibits on Checkbox not workingI have form with a checkbox and a date picker. Neither are required but both should never be fillablAutomatic count repeater itemHello, I tried to count how many items the user input in the repeater so that at the end of the formFont used in FilamentHello, Could anyone please help me identify what font is used in the filament website/package? ThaDisable resource form while editing but enable relation managers?Is this possible without manually disabling each field? What would be the best approach for this?Add CSS class to action formIs there a way to add an extra CSS class to a form of an action? I want to have some custom stylinunique Validation two colums How do itI have two columns I wanaa unique Validation in textinputCount same relationship in multiple columnsI want to have some columns counting the same relationship, but with a few differences, such as diffAdd an Edit button in a view pageIs there a way to add an Edit button yo a view page?