Starting an import does not yet mean that all rows have been saved. In the browser, check both the import log and the saved items' details before running a corrective import.

Find and open the correct import log

In the browser's main menu, open History → Import logs. Check the logs in this browser view; item details shown in the Android or iOS app do not replace checking the log.

Log visibility depends on your permissions. An administrator can view all import logs, but with restricted permissions you can only see your own logs. A missing log therefore does not mean that another user has not started an import. If necessary, ask the user who performed the import or an administrator to check the run.

Find the correct run by its data type, time and user. You can filter the list using the filters below the Imported resource, Start time, End time and User column headings. Open the log details by clicking its link in the Imported resource column.

The list also shows other batch operations, such as contract price changes and reversals. Check the data type before interpreting a log as the result of an Excel import. Contract price processing is described in Contract billing and price changes.

Check completion and row counts

The times, user and row counts appear at the top of the opened log. Start time is the time the log was created. An import may be processed in several batches in the background, so all results may not appear immediately.

End time is filled in when the number of recorded result rows reaches the expected number for the import. Completion does not mean that there were no errors: failed rows also count as processed results. If the end time is missing, the run may still be waiting for processing, be in progress or have stopped before completion. Close the log and reopen it later. If the situation persists, investigate the run before starting a new import.

  • Successful rows: the total number of new and updated items recorded as successful.
  • Failed rows: result rows recorded as failed.
  • Total rows: the expected number of import rows submitted for processing, rather than the number of all physical rows in the Excel file.

For example, if an import of ten rows creates three new items, updates five existing items and fails on two rows, the log shows 8 successful rows, 2 failed rows and 10 rows in total. The import has only partially succeeded, even if the end time has been filled in.

Read the breakdown and verify the saved data

Below the row counts, open New items, Updated items and Failed items by clicking each section heading. The Updated items section is not shown for tag imports. The New items section is not shown for contract price runs.

The failed items breakdown shows the Row number and Error message columns, along with identifying details for the item. Row numbering starts at one and refers to the row where the item appeared in Spotilla's import table just before the import was started. Headers or extra blank rows in the file may affect how this corresponds to the Excel row number. Also identify the row to correct by its name, product identifier or other information shown in the breakdown.

A successful row count does not replace checking the item's details. For example, open a Spot or product name link in the New items or Updated items breakdown and compare the relevant fields and associations with the intended result. A Spot may be saved successfully even if a tag reserved for another item is not attached; this type of problem may not increase the failed row count.

In older logs, the counts and breakdowns may be based on an earlier storage method, and the breakdown may contain less detail. An empty or missing breakdown alone does not show that the import succeeded without errors.

Correct only the necessary data

Read the error messages for the failed rows and correct the issues they identify in the source data. Keep the error message content and the import's data type, time and user if you need help investigating.

Successful items remain saved even if other rows fail. Viewing the log does not undo the import's changes.

Do not automatically import the entire file again if some rows succeeded. First establish whether the import you are using identifies existing data or creates new items. Otherwise, the same data may be processed twice.

A product import creates new products. The By folder import for Spots, in turn, updates a Spot found by its identifier or creates a new one if no matching Spot is found. Check the import method and identifiers before importing again. Follow the instructions for the function you used: Excel import and bulk changes for Spots or Product import, export and bulk changes.

After the corrective import, check its own log and the corrected items' details and associations. Make sure that the necessary changes were saved and that no extra items were created.