How to Re-run a Saved Import Mask in EDGEBIC

To re-run a saved import mask in EDGEBIC by User Solutions you select the mask under Saved Masks, click Do It, point it at the current file if prompted, and read the result counts. Building the mask is the one-time effort; re-running it is the routine you repeat every week, and it is deliberately down to two clicks.

This is the recurring-run task. For what a mask is and how it stores your mapping, read import masks explained, and for building one in the first place, how to build an import mask.

Before You Start

• The mask already exists, saved from an earlier import of the same file shape.
• This week's file matches that shape: the same columns, in a format the mask understands.
• You can see the Settings tab.
• You know whether this run should update existing records, which is set once in the mask's Options and remembered between runs.

Re-running the Mask

1. Open the Settings tab and click the 📥 Import tab.
2. Select the Entity Type the mask belongs to, then pick the mask under Saved Masks.
3. Click ▶ Do It. If the remembered file path still resolves, the run starts against it. If the path is stale, a file picker opens: choose this week's file.
4. Watch the Importing… progress window. On a large file it shows a row-of-total count; on a small one it completes quickly.
5. When it finishes, the Import Result dialog opens with the summary line and one grid row per file row.

If you want the mask to remember a new file location permanently, open it with ✏️ Edit…, click 📂 Get File, pick the new file, and Save. The mapping is untouched; only the stored path changes.

What Changes When You Save

A re-run applies the same mapping to new data. Because every strategy matches on a natural key, existing records are updated or reused, never duplicated.

For entity types with their own behavior, re-running stays safe: BOR routings are wiped and recreated identically, and actuals overwrite the same days with the same values. Imports never recalculate the schedule; run the scheduler afterward if the data you loaded should change the plan.

How to Check It Worked

Read the summary line on the Import Result dialog: Created … · Updated … · Reused … · Failed …. On a steady weekly file, most rows should be Reused (or Updated if that is the run's purpose), with few or no Created and no Failed. Any failures are listed in the grid, and 📄 Open Log File gives the exact rows and reasons. Each run writes its own log file to the EDGEBIC import-logs folder, so you always have a record of what each Monday's run did.

Why Deduplication Makes a Re-run Safe

The reason you can run a mask against this week's file without fear of doubling your data is that every import strategy matches on a natural business key before it decides what to do with a row. A product is matched by its id, a work center by its id, a sales order by its reference, a holiday by its name and date. A row whose key already exists in EDGEBIC comes back Updated (if updates are on) or Reused (if not), never Created a second time. Matching ignores case, so a file row WIDGET-A still finds the existing Widget-A.

That guarantee extends to the entity types with special behavior. A BOR routing re-import wipes and recreates the product's steps, so running the same file twice leaves the routing identical. An actuals re-import overwrites the same days with the same values, so it never double-counts. The practical upshot is that "run it again" is almost always the right move after a fix, rather than trying to isolate only the changed rows by hand.

Building the Weekly Habit

Once a mask is saved, the recurring run is meant to be muscle memory. If the file lands in the same folder under the same name each week, the mask remembers the path and the run is one click of ▶ Do It plus a glance at the counts. If the file moves, the picker catches you and you choose it on the spot. Either way you are not rebuilding anything: the mapping, the sheet, the delimiter, and the options all persist in the mask. A good sign the routine is healthy is a result line that is mostly Reused or Updated with no Failed, week after week; the first week that pattern breaks, the file changed, not the mask.

Common Mistakes

Rebuilding the mapping every week. The whole point of a mask is that the mapping is saved. If you find yourself remapping columns, you are creating a new mask instead of reusing the saved one. Select the existing mask and click Do It.

Blaming the mask when the file changed. A run that suddenly reports failed rows usually means a renamed column, a resaved worksheet, or missing cells. Check the log and the source file, not the mask. This and related traps are in import mask mistakes.

Not noticing a sheet fell back. If an .xlsx worksheet is renamed, EDGEBIC can fall back to the first sheet and read the wrong data. Re-pick the file and reselect the correct sheet.

Assuming a clean run scheduled something. A successful import loads data only. If you imported orders, run the scheduler to plan them.

Correcting a Partial Failure by Re-running

A re-run is also the standard way to fix a run that partly failed. By default a bad row is marked Failed and the import keeps going, so most of your data is already in when you read the result. Rather than picking apart which rows to redo, you fix the problems at the source (a blank key, a malformed number, a name that did not resolve) and run the same mask against the corrected file. The rows that succeeded the first time come back Reused or Updated because they match on their key, and the rows you fixed now go through. Nothing duplicates, and you did not have to isolate the failures into a separate file. On the rare occasion you do want a clean re-run of only the failures, you can filter the source down to those rows, but for most corrections a straight re-run of the whole file is simpler and just as safe.

Next Steps

If a re-run surfaced failed rows, the import said failed rows walks through reading the log and fixing them. The masks you re-run most are usually products and orders. For the full task library, see the EDGEBIC how-to hub, and for the wider platform, EDGEBIC.