Maintenance
This Whitepaper will walk you through the data maintenance process from an administrator point of view. For optimal performance, it is recommended to use clean-up routines to keep data minimal in all historical tables.
For more information on standard D365 maintenance, please visit:
These cleanup routines should be run only after the business has done detailed analysis and confirmed that the data is no longer required. Always test each cleanup routine in a test environment before you run it in a production environment.
Cleanup routines
All our cleanup routines are in the main workspace, under Admin > All Batches > Tasks > Clean, and can be ran manually or via batches.
Automated data maintenance
By default, during the go live procedure, the key user will create Eftsure batches either manually or using the 'Check Batches' button, which automatically creates batches appropriately and depending on your configuration. All batches created will belong to the [Eftsure monitoring category].
As per the screenshot above, the extension will do it's best to prepare these batches, set recurrence and parameters appropriately.
Some batches will be on hold at the time of creation to avoid deleting potential historical data.
Charts cache
This routine calculates the most recent values to display into our charts cache table, which contains a very low number of records.
Run this process as a batch every 15 minutes, as per default generation parameters.
Webservices logs
This routine helps keep the webservices logs size to a minimum, by allowing to delete old archived data. Enter the number of days of data you wish to keep and run the job.
During normal operations, we recommend to keep webservices log turned off, otherwise to keep a maximum of 2 weeks of data and run this job on a daily / weekly basis
Vendor History
This routine helps keep the vendor history table to a minimum in order to avoid huge historical data. By default, this routine is turned off as it would delete historical data that can be used to retrace vendor management lifecycle or use in audits.
It requires to be manually enabled before processing, we recommend to keep an average of 2y of data.
Batch Jobs
This routine helps keep the batch historical data to a minimum for Eftsure batches in the Eftsure monitoring category. It is recommended to match this number of days to your normal batch maintenance, otherwise keep 2 weeks of batch historical data.
