6
When running the Purchase update history cleanup job, there is no way to properly run it on a recurring basis. This is because the the job is run based on a "Created until" date that is specified in the job parameters. As a result, if August 31, 2021 is selected and the job is scheduled to run every week, then the job will only continue to clean up history for purchase orders up to August 31, regardless of the fact that it is recurring weekly.
It would be much more valuable to have a parameter identifying the number of "Days of history to retain". This would allow the job to delete history that exceeds the parameter each time the job is run, thus allowing for a recurrence to be set.
The current functionality requires an administrator to manually schedule the job each time it needs to be run for each legal entity. This is unnecessary and cumbersome, especially for organizations with many operating legal entities.
It would be much more valuable to have a parameter identifying the number of "Days of history to retain". This would allow the job to delete history that exceeds the parameter each time the job is run, thus allowing for a recurrence to be set.
The current functionality requires an administrator to manually schedule the job each time it needs to be run for each legal entity. This is unnecessary and cumbersome, especially for organizations with many operating legal entities.
STATUS DETAILS
Completed
Administrator on 12/10/2021 10:51:50 AM
Thank you very much for your input. We are pleased to inform you that this capability will become available both for Sales order update history cleanup aswell as for purchase order update history cleanup in version 10.0.25.