FilamentPHP Order Total Price Calculation Fails on Creation but Updates on Edit

Below is an explanation of how you might fix the issue along with some code adjustments. In your case the problem is that the parent state (total_price) isn’t being updated on creation because the state paths for new records aren’t the same as when editing an existing record. This often happens when using nested (repeater) fields with relative state paths.

Below are a few suggestions:

---

1. Verify and Adjust the State Paths

In your afterStateUpdated callbacks for the repeater’s subfields you’re using a relative path (“../../total_price”). When creating a record, the state hierarchy may be different from when editing an existing record. One simple fix is to verify that the parent field is accessible at the expected path. If your total_price field is defined on the same form as the repeater, then you might simply call:

PHPCopied
$set('total_price', $totalItems + $totalPackages);

instead of

PHPCopied
$set('../../total_price', $totalItems + $totalPackages);

Test out which state path is correct by logging or debugging the state keys when creating a new order.

---

2. Make Your Total Price Field Reactive

Ensure that your total_price field is reactive so that its value updates as soon as related data (repeater items) changes. For example, when defining the total_price field in your form you might do:

PHPCopied
TextInput::make('total_price')
    ->disabled()
    ->reactive()
    ->label('Total Price')

This guarantees that when your callback uses $set to update total_price, the new value is immediately visible in the UI.

---

3. Consider Using Form-Level Callbacks

Another option is to move the total price calculation to a form-level callback (using something like an afterStateHydrated or a dedicated computed field) that runs on every update of the form’s state. For instance, you can add an afterStateUpdated to the repeater field itself. That way, any time items or packages change, you recalculate and set total_price. Example:

PHPCopied
Repeater::make('items')
    ->relationship('items')
    ->afterStateUpdated(function ($state, $set, $get) {
        // Calculate totals from both repeater fields.
        $items = $get('items') ?? [];
        $packages = $get('packages') ?? [];

        $totalItems = array_reduce(
            $items,
            fn ($carry, $item) => $carry + ($item['subtotal'] ?? 0),
            0
        );

        $totalPackages = array_reduce(
            $packages,
            fn ($carry, $package) => $carry + ($package['subtotal'] ?? 0),
            0
        );

        // Use the correct state path to update total_price.
        $set('total_price', $totalItems + $totalPackages);
    })
    ->schema([
        // ... your fields as before ...
    ])
    ->label('Selected Menus')
    ->collapsible()
    ->defaultItems(1)
    ->addActionLabel('Add Menu');

This ensures the parent total_price is recalculated and updated on every change in the repeater.

---

4. Double-Check the Order of Evaluation

Depending on which field changes first (the menu selection or the quantity) you might be reading an outdated state for one of them. Make sure your callbacks use the current values from the repeater item rather than relying on a specific order. It sometimes helps to “chain” the recalculation from one common callback (as shown above) rather than updating the parent field from each individual subfield callback.

---

Summary

The reason total_price remains 0 on creation is that your afterStateUpdated callbacks aren’t updating the parent total_price field as expected when creating a new record. Adjust the relative state path (or use the absolute path where total_price lives), make the total_price field reactive, and/or centralize your calculation at the form level so that it runs regardless of whether you’re creating or editing an order.

Try one or a combination of the above changes. This should result in the total_price being calculated and displayed immediately on the order creation screen.