It creates confusion for the end users when batch jobs completes with the status of "Ended" but when you review the log there are errors. This is a very time consuming process to have to review each batch job's log to see if there are errors. We understand the need to differentiate between an error that stops processing and one that allows processing to continue through other records. In our case, we definitely want the job to continue processing through the remaining records. It seems to us that there should be 3 different statuses instead of just 2:
- One to indicate that a batch job finished successfully without encountering any errors.
- One to indicate a batch job finished successfully, but with some errors.
- One to indicate a “hard” error was encountered and processing has stopped.
It would also be nice to be able to set alerts on the batch job that it has ended, but there are errors.
Comments
This really needs to be taken care of by Microsoft!We have a situation with a customer that is doing a LOT of processing through batchjobs which means they have 1000+ jobs with multiple batch tasks, which would mean that the customer must go through 5000+ infologs every single day 7 days week all year.It should be obvious to everyone that this solution isn't really a solution especially because D365 Finance and Operations are marketed as and aiming at being an Enterprise ERP solution.I like the idea with the 3 statuses and a supplement could be that when starting a batch job, you had some way of indication what level of error handling you wanted for the given batchjob.
Category: System administration