โ ๏ธ DO NOT perform this task if your database is already in production.
Purging permanently deletes data and cannot be undone. If you do perform this task, review the data that will be affected at the bottom of this article. If on premise, its important to backup the Microix database before performing the job.
๐ซ Microix automatically prevents purging if the system contains 100 documents or more.
Purge is only available when the system contains fewer than 100 total documents.
๐ This action must only be performed by an administrator with the required permissions.
If the user is not granted access to the Bulk Update function, they will not be able to complete this process.
Once completed, all practice/test transactions will be removed, allowing you to proceed with go-live using a clean database (as long as the system is under the 100-document threshold).
The Purge Documents process removes all records across several functional areas. The table below summarizes the data impacted:
| Category | Table(s) Affected | What This Removes |
|---|---|---|
| Inventory Related Data | Inventory Ledger (Movement) | Inventory movement records created during practice transactions |
| Inventory Related Data | Items by Location | Items assigned to a Location |
| Inventory Related Data | Physical Count Data | Physical count records |
| Timesheet Related Data | Time Clock Data | Punch clock entries created during testing/training phase |
| Bank Feed | Credit Card Transactions | Credit card data from import or bank feed |
| Reimbursements | Reimbursements Transactions | Reimbursements transactions not processed (if enabled) |
| Invoice Capture | Captured Invoices | All captured invoices (if enabled) |
| Attachments | File Attachments | Attachments associated with practice/test documents |
| All Documents | All document types for Purchase Order, Invoice, Timesheet, Adjustments, and Budget (up to 100) | Document records removed during purge (system will not purge above 100 documents) |