Skip to content

How do I review an import and correct what failed?

Every import is recorded with its count and the details of the rows that didn’t go in. This page explains how to read that report, what each status means and how to repeat the import fixing only what failed.

Where can I see what was imported?

In Management › Data import, History tab. There is one row per import, from the most recent to the oldest, with the file name, the target, the source type, the status, the total number of rows, how many were imported, how many gave an error and the date.

Both the imports you ran by hand and the ones a scheduled task ran are there.

The View issues button on each row opens the details: row number, status and reason. The number is the row number in the file not counting the header, so row 1 in the report is the second row in the Excel file.

The history belongs to the company you are in. Imports from another company can’t be seen from here.

What does each status mean?

The status of the whole import can be:

The status of each row can be:

How do I correct the rows that gave an error?

They aren’t edited from the programme: you correct the file and import it again. The procedure is always the same and it is safe to repeat it in full, there is no need to cut the file down to the bad rows:

  1. Open View issues and note down the row numbers and the reasons.
  2. Correct those rows in the original file.
  3. Go back to the wizard, load the corrected file and repeat the import with the same target and the same template.

Rows that had already gone in are recognised by their key. With the Reset existing box unticked they are skipped; ticked, they are updated with whatever the file brings. In neither case are they duplicated.

Each attempt creates a new entry in the history: earlier reports aren’t overwritten.

Can an import be undone?

No. There is no command that reverses what has been imported. The records created stay, and to remove them you have to delete them one by one from their own screen.

This also applies to indirect effects. An imported delivery note that moved stock doesn’t give it back when you delete the history entry: you have to void the delivery note.

That is why, when the volume is large or the file comes from an unknown system, it is best to:

Why does a row ‘with errors’ say the ERP rejected it?

There are two moments at which a row can fail, and the message tells them apart.

The first is validation: the programme checks that the required fields are there, that the key isn’t missing or repeated within the file and that the Tax ID is valid. These are messages like ‘“Nombre” is required and is empty’.

The second is writing: the row was correct on paper, but the ERP didn’t accept the record when creating it. Those messages start with ‘Error writing:’ and bring the reason given by the module concerned: a customer code repeated with another record, an unbalanced journal entry, an item that doesn’t exist when its prices are imported.

Writing errors are row by row. One doesn’t cancel the others: each record is saved on its own, and the ones that go well stay saved even if a later one fails.


See also: Import customers from an Excel file · What can be imported · Schedule a recurring import

More about Bring in your data