What Is an Import Row Status?

An import row status is the outcome EDGEBIC assigns to each individual row of an import file: Created, Updated, Reused, Skipped, or Failed. It is how you tell, row by row, what an import actually did, rather than trusting a single overall count. The result summary tallies each status, and the run log records the outcome and reason for every row, so a load is never a black box.

EDGEBIC by User Solutions assigns a status to every row as it is processed and rolls them up into a result summary. This article defines the five statuses. For the create-or-update logic behind three of them, see the sibling term upsert.

How It Works

As the import processes each row, it decides what happened and stamps a status on it:

• Created: the row was a new record, added and saved.
• Updated: the row matched an existing record and changed it.
• Reused: the row matched an existing record and left it unchanged, typically because the mask has updates turned off.
• Skipped: the row was internal bookkeeping rather than a business outcome, such as an intermediate step during a two-pass routing import.
• Failed: the row could not be processed, usually because a mandatory value was blank.

The result dialog sums Created, Updated, Reused, and Failed so you see the shape of the load at a glance. Skipped rows are hidden from that on-screen summary, because they are noise for a planner, but the run log keeps every row including the skipped ones for a complete record.

What happens after a failure depends on a mask option. By default the import continues past a bad row and processes the rest, tallying the failure. If you set it to stop on the first error, a failure aborts the run and leaves later rows untouched. Rows already saved before the abort stay saved.

A Concrete Example

Think of grading a stack of forms at a front desk. Each form gets a stamp: "new file created," "existing file updated," "matched, nothing to change," "internal slip, ignore," or "rejected, missing signature." At the end of the day, you count the stamps to know how the batch went, and the rejected forms sit in a tray with a note explaining why.

In EDGEBIC, a product load might report:

Summary: three real outcomes and one failure, with the failed row and its reason waiting in the log for correction and re-run.

How EDGEBIC Uses It

Row status is the language of the import result and the run log. The result dialog shows the tallies right after a run, and the log, written to disk for every import, records the status and detail of each row for later review. Together they let you confirm a clean load or pinpoint exactly which rows need attention.

Because imports match on a business key, re-running a corrected file is safe: previously successful rows come back as Updated or Reused rather than duplicated, and only the fixed rows change status. If a routing import's visible count looks low, that is the hidden Skipped bookkeeping from its two-pass process, not lost data; the log confirms it. For the outcome logic in detail see how EDGEBIC handles import masks, and for what to do about failures see the import said failed rows. Browse more definitions in the manufacturing glossary.