How to Clear Test Data Before Going Live in EDGEBIC

To clear test data before going live in EDGEBIC by User Solutions you back up first, open the Clear Data Tables utility from Data Management, pick either selected tables or a full wipe, type CLEAR to confirm, and restart on the clean database. This is a permanent, no-undo action, which is exactly why the backup comes first, every time.

This is the going-live housekeeping task. For the backup that must precede it, see how to back up the EDGEBIC database, and for the wider install and connect flow, how to install and connect EDGEBIC.

Before You Start

• You have taken a backup. Clear Data has no recycle bin. Click Export on the DataSource tab first.
• You are signed in as an administrator, or with a role that includes the Clear Data permission, which is intentionally administrator-only.
• You have decided the scope: keep the master data you built and clear only test transactions, or wipe everything and start empty.
• No one else is mid-task against a shared database. On SQL Server this affects every connected user.

Clearing the Data

1. Open the Settings tab and click 🗑️ Data Management, then 🗑 Open Clear Data Tables…. (The main toolbar's Reset to Default button opens the same dialog.)
2. The Clear Data Tables dialog opens under a red Hard-Delete Data Tables banner, because this permanently removes rows.
3. Choose the mode:
   • Clear Selected Tables to remove just the areas you tested with. Tick each area, and expand its row to see exactly what else it cascades to before you commit.
   • Clear ALL Data (full database wipe) to empty everything: schedules, actuals, orders, quotes, sales orders, products, BORs, work centers, departments, shifts, holidays, and per-user UI configurations.
4. User accounts survive unless you additionally tick Also clear Users & Sign-in Audit (administrator will need to be re-created). Leave it unticked to keep your sign-ins.
5. Type CLEAR in the confirmation box, then click 🗑 Clear Data.
6. Watch the progress. On success the dialog offers 🔄 Restart Now, or counts down to an automatic restart.

What Changes When You Save

The clear runs as one operation, so a failure rolls the whole thing back rather than leaving you half-cleared.

The permission catalog and role definitions always survive, because they are re-seeded on the next launch. If you clear users on a full wipe, the founding administrator is gone and you are prompted to create a new one at next startup, exactly as on a fresh install.

Selected Tables Versus a Full Wipe

The two modes suit two different going-live situations, and choosing well saves rework.

Clear Selected Tables is for when you built real master data during setup or training and want to keep it. You tick only the transactional areas (schedules, actuals, orders, quotes) and leave products, work centers, routings, shifts, and holidays untouched. The result is the plant you configured with an empty schedule, ready for the first live orders. Expanding each ticked row before you commit is important here, because clearing schedules also removes the allocations and breakdowns tied to them, and clearing orders reaches the sales orders behind them. What cascades is shown in the dialog so there are no surprises.

Clear ALL Data is for a genuine fresh start: a demo you want to wipe, a training database you are done with, or a clean slate you would rather rebuild from imports. It empties everything operational, including per-user screen layouts. It does not touch user accounts unless you additionally tick the clear-users option, and it never removes the permission catalog or role definitions, which are re-seeded on the next launch. So even a full wipe leaves the security framework standing unless you deliberately choose otherwise.

A useful rule of thumb: if you spent hours entering products, work centers, and routings that are correct for production, use Selected Tables and keep them. If the whole database is throwaway, a full wipe is cleaner than picking scopes.

A Quick Worked Example

A team spent a training week building their real plant in EDGEBIC and now wants to go live with the setup but none of the practice jobs. The administrator clicks Export on the DataSource tab for a backup, then opens Settings → 🗑️ Data Management → 🗑 Open Clear Data Tables…. He chooses Clear Selected Tables, ticks schedules, actuals, and orders, and expands each to confirm what it cascades to. Products, work centers, routings, shifts, and holidays stay unticked. He types CLEAR, clicks 🗑 Clear Data, and takes the 🔄 Restart Now offer. After restart, Drive Schedule and the Gantt are empty, but the plant he built is intact, and the first real order can be imported and scheduled against clean history.

How to Check It Worked

After the restart, open the areas you cleared and confirm they are empty: an empty Drive Schedule and Gantt after clearing schedules, or empty product and work center grids after a full wipe. If you kept master data, confirm it is still present and correct, because that was the point of a selective clear. If you cleared users, you should meet the create-administrator dialog on startup. Keep the backup you took until you have confirmed the result is what you intended.

Common Mistakes

Running it without a backup. There is no undo. The one habit that makes this safe is an Export beforehand, every time.

Mistaking Reset to Default for a layout reset. That toolbar button opens the Clear Data dialog, which can clear tables. Nothing is deleted until you pick scopes, type CLEAR, and click Clear Data, but read the dialog before confirming. To reset only layouts, clear just the UI configurations scope, or use a view's own Reset to Defaults.

Choosing a full wipe when a selective clear was meant. If you built a plant during training and want to keep it, clear only schedules, actuals, and orders. A full wipe throws away the master data too. Related pitfalls are in deployment and database mistakes.

Clearing users by accident. The clear-users option is separate for a reason. Leave it unticked unless you genuinely want to reset the sign-ins and re-create the administrator.

Running it on a shared database mid-shift. On SQL Server the clear hits everyone. Coordinate the timing before you confirm, and see moving from single-user to shared server for how the shared setup behaves.

Next Steps

Once the database is clean, you rebuild master data with the import masks: products and work centers first, then routings and orders. And keep the backup habit with how to back up the EDGEBIC database. For the full task library, see the EDGEBIC how-to hub, and for the wider platform, EDGEBIC.