One of my customers pinged me a while ago and mentioned that she had notifications in her Dynamics 365 Finance and Supply Chain environment saying that she was missing some batch jobs.
- Scan for orphaned document references
- Scan for document files that have been scheduled for physical deletion
- Scans for temporary files that have expired
- Deletes expired email history.
- Recommendation batch job
All jobs had to do with optimizing how the solution works and are all part of Microsoft Best Practice… that means that if you are contacting support and have a performance related issue, this is one of the tasks you might get.
First of all, we need to take a step back and think about why these jobs are needed. Since FnO is a cloud hosted “SaaS” solution, we have access to a limited amount of performance and one of the reasons for running optimization and clean-up jobs in the solution is to keep it performant. We also pay for storage capacity, or at least we will once the new environments based on the Power Platform architecture is in full swing and keeping the database and storage lean means that we are paying less.
Back to the issue at hand… There are 5 batch jobs the system is saying are best practice. To enable these, you can eighter just go to the Batch Jobs in your system and set them to waiting, or you can just click the link in the notification to enable them. In my case there was actually one job missing from batch jobs and in that case the job was recreated and set to waiting.
Besides the batch jobs I would recommend you to set up the clean-up jobs documented on Microsoft Learn and you should also read up on the new features coming for archiving and long term Retention.