Laravel-excel: [PROPOSAL] Import items without saving directly

Using ToModel is just one way of dealing with imports. This is just option that makes 1 model per row inserts easier.

If you want to handle different structures and in a way that it's similar to version 2.1, than you need to use ToCollection: https://laravel-excel.maatwebsite.nl/3.1/imports/collection.html In the collection method you get a similar collection of rows that you got in 2.1.

If you want get the models only in the controller and not in your import object (not really a recommended approach) than there's the ::toCollection method, which returns the raw row (no conversion to models is done) to your controller.
(https://laravel-excel.maatwebsite.nl/3.1/imports/basics.html#importing-to-array-or-collection)

$users = Excel::toCollection(new UsersImport, 'users.xlsx');

@patrickbrouwers thanks for your reply. So if I understand correctly, using Excel::import on an import that implements ToCollection will return a collection of models without saving them? If so, this is not clearly stated in the documentation, as the example at the bottom of https://laravel-excel.maatwebsite.nl/3.1/imports/collection.html is as follows:

public function import() 
{
    Excel::import(new UsersImport, 'users.xlsx');
}

The return value isn't stored anywhere, implying that the imported collection of models is saved directly (or at least that the method has side-effects). Otherwise it would be useless calling import without assigning the return value to a variable right?

@WouterFlorijn No, ::import() will never return any rows or models. Only Excel::toCollection() does.

Using the ToCollection concern is something different than using Excel::toCollection().
When implementing ToCollection the entire import is encapsulated within the Import object. Returning something in ToCollection won't be returned to the controller.

@patrickbrouwers Just to get back, I still think we're misunderstanding each other. What I'm simply looking for is a method that returns a Collection of Models, without saving them. I don't want to process the rows in my controller, I would like to do that in an Import class. So far I haven't found this.

The idea:

TransactionsImport.php:

<?php

namespace App\Imports;

use App\Banks\Transaction;
use Carbon\Carbon;
use Maatwebsite\Excel\Concerns\ToModel;
use Maatwebsite\Excel\Concerns\WithHeadingRow;

class TransactionsImport implements ToModel, WithHeadingRow
{
    public function model(array $row)
    {
        $transaction = new Transaction;
        $transaction->amount = $row['amount'];
        $transaction->currency = $row['currency'];

        return $transaction;
    }
}

TransactionsController.php:

...
$transactions = Excel::someFunction(new TransactionsImport, 'path/to/file.csv');
// $transactions is a Collection of Transaction models that are not saved to the database yet.
...

I also found two issues with the toCollection function:

1. It returns a Collection with a single item, which is another Collection that contains a Collection for each row.
2. It takes an import argument, which is useless in cases where you just want to return the rows as Collections.

What I'm simply looking for is a method that returns a Collection of Models, without saving them. I don't want to process the rows in my controller, I would like to do that in an Import class. So far I haven't found this.

Perhaps these docs are helpful to you:
Handling persistence on your own
Architecture Concepts

@WouterFlorijn you can try this approach to get an array from your file:

$array = Excel::toArray([], 'file.xlsx');

@WouterFlorijn you can try this approach to get an array from your file:

$array = Excel::toArray([], 'file.xlsx');

That's exactly what I was looking for.

+1 for this request. I don't think the model() and collection() methods should save anything. It should return the data from an Excel/CSV file into a Collection (or Array) of Models/Arrays. Persistence should be handled separately, or at least be a choice.

My use case: I want to get the min and max date from records in a CSV. If this overlaps with an existing imported CSV, it should not import anything before the user confirms that the overlap is correct.

Edit: Ah, I am responding to a closed issue. How did you handle this @WouterFlorijn?

You can easily achieve this yourself already by keeping state inside the import class, you could wrap up the toModels method inside a trait and re-use it in all your exports.

new UsersImport implements ToModel, WithHeadingRow
{
    use Importable;

    protected array $models;

    public function model(array $row)
    {
         $this->models[] = new User($row);
    }

    public toModels(string $filename): array
    {
       $this->import($filename);

        return $this->models;
    }
}

$nonPersistedUsers = (new UsersImport)->toModels('users.xlsx');