Archive and Purge data from Dynamics AX - Screenshots from Ignify

Data Archival for Dynamics lets you setup different data reduction procedures i.e. purge or archive for different transaction entities e.g. (Sales Orders,  Purchase Orders, General Ledger etc.  For example in the screen below, sales orders for all companies are being archived along with all related transaction sub-entities including Sales Order Confirmation, Picking list, Packing Slip, Sales Order Invoice  while Purchase orders are being purged for a single company.

Data Archival for Dynamics provides you with best practice rules out-of-the-box while archiving or purging entities. This ensures that you do not unknowingly archive open transactions or leave orphaned records in your database. In the screen shot below, the best practice recommendations to archive a Sales Order are that the.

• Sales Order should be fully paid
• Invoice for the Sales Order should be fully paid
• Sales line inventory should be closed

The application contains these best practice rules as defaults. However it provides the ability for a user to override these rules

Filter criteria such as data range, customer group/ vendor group, status can be applied during archival or purged. For example, we are archiving all Sales Orders between January 1, 2002 to December 31, 2007 in the screen shot below.

Data Archival for Dynamics allows you to identify and validate the transactions that will be purged or archived before the archival/ purge process runs. In this example, we can see the purchase order numbers for all the purchase orders that are going to be archived prior to running the archival process.

Data Archival for Dynamics lets you schedule your data reduction operations so that they can run automatically. The data archival procedure can be set to run at a future date for a one-time operation or for a repeating periodic operation with varying frequencies (daily, weekly, monthly, or a certain number of months in a year). Different operations can be scheduled at different times. For example, you could schedule a Purchase Order purge to happen once a week and a Sales Order archival process to run every month.