How to Edit or Delete a Saved Import Mask in EDGEBIC

To edit a saved import mask in EDGEBIC, open Settings and the Import tab, select the mask's entity type in the Entity Type list, select the mask under Saved Masks, and click Edit; to retire one, select it and click Delete Mask. Both buttons sit on the same toolbar as Define New and Do It. In EDGEBIC by User Solutions a mask is a saved mapping and nothing else, so editing changes a recipe and deleting removes a recipe. Neither one touches data a previous run already loaded.

This is the maintenance task, not the build. For creating a mask from nothing, start with how to build an import mask; the full task library is on the EDGEBIC how-to hub.

Before You Start

• You know which of the eight entity types the mask belongs to. The Saved Masks grid is filtered by the entity type selected on the left, so a mask you cannot find is usually a mask you are looking for under the wrong type.
• You have the current version of the source file to hand if the reason for the edit is that the file changed.
• You know that a mask edit overwrites the previous mapping with no version history, so the old mapping is gone the moment you save.
• You have access to the Settings tab, which is permission controlled.

The Steps

1. Open Settings, then the Import tab. The Import Data page opens with the Entity Type list on the left and Saved Masks beside it.
2. Select the entity type the mask belongs to: Product, Workcenter, Customer, SalesOrder, BOR, Actuals, PlantHoliday, or Shift. The Saved Masks grid refreshes to show only that type's masks with their name, last file, and format.
3. Select the mask you want to change.
4. Click Edit. The mask editor reopens with everything you saved: the Name, the remembered file and worksheet, the format options, and the field mappings grid.
5. Make the change. The three edits that come up in practice:
   • The file moved or its headings changed. Click Get File and pick the current file, then reselect the worksheet in the Sheet box. The file-headers list refreshes, and you drag the new headings onto the target rows that need them.
   • A number arrives in different units. Set or clear the conversion factor on that mapping row. A source column in minutes needs 0.016667 to land as hours.
   • The routine changed name. Edit the Name so it still describes the routine rather than a file that no longer exists.
6. Save. The mask row updates in the grid and the next Do It uses the new mapping.
7. To retire a mask instead, select it and click Delete Mask. It disappears from that entity type's list.

What Each Button Actually Changes

The three mask buttons look adjacent and do genuinely different things. Reaching for the wrong one is the most common wasted trip on this screen.

How to Check It Worked

Read the Saved Masks row first. Its name, last file, and format should now show what you intended, and a mask that still lists last week's file was not saved.

Then prove the mapping rather than assuming it. Run the edited mask with Do It against a short slice of the real file, ten rows is plenty, with update existing records left off. Read the summary line on the result dialog: created, updated, reused, and failed counts. On a mask you only remapped, a slice of already-loaded records should come back as reused with zero failures, which tells you the natural key still resolves. Open the log file from the result dialog if any row failed, because it names the row number and the exact reason. The disciplined version of this check is set out in testing an import mask change before the live run.

For a deletion, confirm the mask is gone from the list and that the mask you kept is still there. Then run the survivor once so you know the routine still works without the mask you removed.

Common Mistakes

Hunting for a mask under the wrong entity type. Masks are scoped to the entity type selected on the left. A sales-order mask is invisible while Product is selected, and the usual reaction is to build a duplicate. Change the entity type before you conclude a mask is missing.

Unmapping a required row and saving anyway. Rows ticked as required must be mapped for the mask to run. Clearing one during an edit produces a run that aborts immediately with no rows processed, which reads like a file problem and is not. Reopen the mask and remap the required row.

Expecting Edit to show the run options. The options are behind their own dialog, so a planner who edits the mask and then complains that nothing updates has usually not turned on update existing records. See how to set import options for a mask.

Editing without recording what changed. There is no version history on a mask, so six months later nobody can explain why an hour total shifted. One line per edit is enough, and keeping a change log of import mask edits sets out the fields worth capturing.

Deleting a mask to reset it. Deleting and rebuilding is slower than editing and loses every mapping decision you got right. Delete when a routine genuinely ends, not when one column has moved.

Accumulating a mask per file. Masks named after files multiply until nobody knows which is live. One mask per recurring file shape is the standard, and how many import masks your shop actually needs puts a number on it.

Next Steps

Once the mask is right, the run is two clicks: see how to re-run a saved import mask. If the reason for the edit was a restructured extract, the failure mode to understand next is a shifted column order, covered in handling an ERP export that changed column order. And if the edit was about units rather than columns, how to convert minutes to hours during an import covers the conversion factor properly.

The takeaway

Editing a saved import mask in EDGEBIC is four clicks: select the entity type, select the mask, click Edit, and change the file, name, mappings, or conversion factors before saving. Delete Mask retires a mapping without touching a single imported record, and the run behavior lives behind the separate options dialog. Because a mask edit overwrites the old mapping with no history, prove the change on a ten-row slice with updates off before the full file, and write down what you changed. See where the import machinery sits in the platform on the EDGEBIC overview, read what carries forward from your existing system on the RMDB to EDGEBIC guide, and continue with how to build an import mask and how to re-run a saved import mask.