How to Set Import Options for a Mask in EDGEBIC

Setting import options for a mask in EDGEBIC by User Solutions means opening the Options dialog on the Import tab: it holds the checkboxes that decide whether a run updates or reuses matches, stops or continues on a bad row, auto-creates missing records, and how actuals are treated. The options are saved with the mask, so you set them once per routine. Here is what each one does and when to change it.

For building and running masks, see how to re-run a saved import mask and how to import products from Excel. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• A saved mask exists for the entity you are importing. Options are per mask.
• You know what the run is for: a first-time load, a value refresh, or an actuals log. The purpose decides the options.
• You can reach the Settings tab, since Import lives there and is permission-controlled.

Step 1: Open the Options Dialog

Open the Settings tab, click the Import tab, select the mask under Saved Masks, and click Options. The Import Options dialog opens with a set of checkboxes. Which ones appear depends on the mask's entity type: a product mask shows the general options, while an actuals mask adds several of its own.

Step 2: Set the Two Options Every Mask Has

Two options apply to essentially every import, and they are the ones most worth getting right.

Leave UpdateExistingRecords off for a first-time load so nothing existing is disturbed. Tick it only when the run's job is to change values, such as a price or credit-limit refresh. Leave ContinueOnRowError on unless you would rather fix the whole file than import part of it.

Step 3: Decide on Auto-Create for Related Records

Some entity types can create related records on the fly rather than failing when a name is not found. These are on by default:

Auto-create keeps a load moving, but it also means a misspelled product name quietly creates a new stub product. If your master data is meant to be complete already, consider clearing auto-create so unknown names fail loudly instead.

Step 4: Set the Actuals-Specific Options

An actuals mask adds toggles that shape how logged hours and pieces land:

The one that surprises people is MarkCompleteOnImport. Clear it when you are logging in-progress hours day by day and do not want each import to close the operation.

Step 5: Close and Run

Close the dialog and click Do It. The options you set are stored on the mask, so every future run uses them until you change them.

What Changes When You Save

The options are saved on the mask, not applied to any data by themselves. Nothing imports until you run the mask. The next run then behaves according to the options: updating instead of reusing, aborting instead of continuing, and so on.

How to Check It Worked

Run the mask and read the result counts against your intent. If you turned UpdateExistingRecords on for a price refresh, you should see Updated counts rather than Reused. If you cleared ContinueOnRowError and the file has a bad row, the run should abort at that row rather than finishing with a Failed count. For an actuals run with MarkCompleteOnImport cleared, the operations should stay in progress rather than showing complete.

Common Mistakes

• Leaving updates off for a refresh. Every row comes back Reused and nothing changes. Tick UpdateExistingRecords when you mean to update.
• Leaving auto-create on with dirty data. A typo creates a stub record instead of failing. Clear it when master data should already be complete.
• Marking actuals complete unintentionally. Clear MarkCompleteOnImport for day-by-day in-progress logging.
• Assuming options are global. They are per mask. Set them on each mask you use.

Next Steps

• Handle unit differences with how to convert minutes to hours during an import.
• Load your shop history with how to import actuals from a file.
• See how imported data becomes a plan on the EDGEBIC product page.