FilamentPHP: total_price is 0 when creating an order, only updates on edit.

FilamentPHP is a popular backend development framework for Laravel that provides a simple and intuitive interface for managing data. In your case, you're encountering an issue where the total_price field is set to 0 when creating a new order, but updates correctly when editing an existing order.

To diagnose and solve this issue, let's follow these steps:

Check the database schema First, ensure that the database schema for the total_price field is correct. You can check this by running the following command in your terminal:

php artisan make:model Order -m

This command will generate a new Order model and a migration file. Open the migration file (located in the database/migrations folder) and check if the total_price field is defined correctly. It should look something like this:

Schema::create('orders', function (Blueprint $table) {
    $table->id();
    $table->decimal('total_price')->default(0);
    // Other fields...
});

Check the Order resource file Next, check the Order resource file (located in the app/Http/Resources folder) to ensure that the total_price field is being returned correctly. It should look something like this:

class OrderResource extends JsonResource
{
    public function toArray($request)
    {
        return [
            'id' => $this->id,
            'total_price' => $this->total_price,
            // Other fields...
        ];
    }
}

Check the Filament Order grid and form Check the Filament Order grid and form to ensure that the total_price field is being displayed and updated correctly. You can do this by opening the Order resource file (located in the filament/src/Resources/Pages folder) and checking the getFormSchema and getTableSchema methods.

class OrderResource extends Resource
{
    protected static string $model = Order::class;

    public static function form(Form $form): Form
    {
        return $form
            ->schema([
                // Other fields...
                Field::decimal('total_price')->label('Total Price'),
            ]);
    }

    public static function table(Table $table): Table
    {
        return $table
            ->columns([
                // Other columns...
                Column::decimal('total_price')->label('Total Price'),
            ]);
    }
}

Check the OrderController Check the OrderController (located in the app/Http/Controllers folder) to ensure that the total_price field is being set correctly when creating a new order.

class OrderController extends Controller
{
    public function store(Request $request)
    {
        $validatedData = $request->validate([
            // Validation rules...
        ]);

        $order = Order::create($validatedData);

        return redirect()->route('orders.index')->with('message', 'Order created successfully.');
    }

    public function update(Request $request, Order $order)
    {
        $validatedData = $request->validate([
            // Validation rules...
        ]);

        $order->update($validatedData);

        return redirect()->route('orders.index')->with('message', 'Order updated successfully.');
    }
}

Make sure that the total_price field is being set correctly when creating a new order. If it's not, you may need to update the validation rules or the data being passed to the create method.

Check the database queries Finally, you can check the database queries being executed when creating and editing orders to see if there's any discrepancy. You can do this by enabling query logging in your .env file:

DB_DEBUG=true

Then, you can check the queries being executed by adding the following code to your app/Http/Kernel.php file:

protected function queryEvent($query)
{
    if (app()->environment('local')) {
        \Log::info("Query: {$query->sql}");
    }
}

This will log all database queries to the console when running your application locally. You can then check the queries being executed when creating and editing orders to see if there's any discrepancy.

If none of the above steps solve the issue, you may need to provide more context or code to help diagnose the problem.