The EDGEBIC Data Clear Tool and When to Use It

The EDGEBIC Clear Data Tables utility deletes data from the scheduling database with no undo, so it is deliberately guarded and paired with a backup habit: use it to reset a training database, clear a demo, or start a fresh planning year, and always export first. In EDGEBIC by User Solutions clearing data is a legitimate and occasionally necessary operation, but it belongs to the small set of actions without a built-in reversal, which shapes everything about how you use it.

This post is the utility and its right moments. For the full reference behind the controls here, read the EDGEBIC admin guide, and for the wider maintenance picture, see keeping the EDGEBIC database healthy over time. It names controls that live in the data-management utilities and on the DataSource tab, never any internal path.

What the Utility Does, and Its Guards

The Clear Data Tables utility deletes data, either selected areas or the entire database. That is a powerful action, and the utility treats it as one. Four guards stand between you and a mistake.

• A red warning banner marks the screen so you always know where you are.
• Selected areas versus a full wipe. You choose whether to clear specific areas, like jobs and schedules, or the whole database, so the common case does not require the nuclear option.
• Expandable cascade previews. Each area expands to show what clearing it cascades to, so you see the downstream effect before you commit rather than discovering it after.
• A separate opt-in for user accounts. Clearing data does not touch your user accounts unless you specifically opt in, so wiping jobs does not accidentally wipe your team.
• A typed confirmation word. The final button does not enable until you type a confirmation word, so the last action is deliberate rather than reflexive.

These guards prevent accidents. What they cannot do is reverse a deliberate clear, because the operation has no undo. That is what the backup is for.

The Backup Is the Undo

The single rule that makes the utility safe is to export a backup before you clear. The documented rule of thumb is to export from the DataSource tab before every data clear, mass routing re-import, or provider switch, because those three operations are the ones without a built-in undo. For the local single-file database the export is one click and creates a timestamped copy even while the application runs. For a shared SQL Server database, confirm IT's rotation has a fresh copy and take an export as well.

The reason to internalize this before you ever open the utility is that the moment you need the backup is the moment it is too late to make one. A clear with an export taken first is a reversible decision. A clear without one is permanent.

When to Use It

Clearing data is the right tool in a short list of situations.

The most common legitimate use is the fresh planning year: you want last year's jobs and schedules gone, but you want to keep the shop model you built (work centers, products, customers, and routings). The selected-areas mode does exactly that. Clear jobs and schedules, read each cascade before committing, leave master data in place, and you begin the year with a clean job list on an intact plant.

When Not to Use It

Just as important is knowing when the utility is the wrong answer. It acts on the whole database it is connected to, so it is not a way to prune a few bad records from a live plant; that is ordinary editing, not a data clear. It is not a way to reset one user's view; that is a layout reset, covered in administering grid layouts. And it is not a substitute for keeping training data separate: if you routinely reset a training class, a separate training database (easy with the portable local file) is cleaner than clearing selected areas out of a shared live database every time.

The general principle is that the utility is for wiping a database or a large area of it, deliberately, as a reset. Anything smaller or more surgical has a gentler tool.

Guards, Permissions, and Backups Together

The strongest protection against a costly mistake is not any one guard but the combination. The utility's guards make an accidental clear nearly impossible. Role-based access restricts who can reach data-management functions at all, so only trusted administrators can open the utility, which is one of the reasons roles matter, as role-based access explains. And the export backup makes even a deliberate mistake recoverable. Guards, permissions, and backups together turn a no-undo operation into a safe, routine part of administration.

For the full set of habits that keep the database dependable, read keeping the EDGEBIC database healthy over time, and for the general planning context these resets support, see what production scheduling is. The full administrator reference is the EDGEBIC admin guide.