Filament 4: After changing Select field type to disable, UI reverts to previous value despite being set to null #18668
Answered
by
anntnzrb
oktavianoandy
asked this question in
Help
-
Beta Was this translation helpful? Give feedback.
Answered by
anntnzrb
Dec 8, 2025
Replies: 1 comment 1 reply
-
|
The issue stems from relationship hydration taking precedence after save. Add |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
oktavianoandy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



The issue stems from relationship hydration taking precedence after save. Add
afterStateHydratedto force null state:->afterStateHydrated(function ($state, $set, $get) { if ($get('type') === TransactionType::income->value) { $set('recipient_id', null); } }). Alternatively, use->saveRelationshipsUsing(fn($get) => $get('type') === TransactionType::income->value ? null : function() {})as suggested in issue #17778. This is an open issue in Filament v4.