web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Clean up the batch job history - does not cleanup any jobs from the Batch History

(1) ShareShare
ReportReport
Posted on by 108
Hello, 
 
I have been trying to clean up the batch job history using the below link:
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/batch-history-cleanup

I am using the regular Batch Job History Clean-up and keeping the history limit days to 15. However, after running the job, it does not delete any jobs for any of the legal entities in the application. Below is a screenshot of an ended run, but there are no jobs deleted.
 
Below is a screenshot shows a message with no log data
I have the same question (0)
  • AK2 Profile Picture
    108 on at
    Clean up the batch job history - does not cleanup any jobs from the Batch History
    Thanks Hana for the response! 
    I looked at the database configure link https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/configure-manage-database-log
    I guess, I will need to setup a logging to see those transactions, however, I see that Microsoft also warns that enabling Database logging, might also result in Performance impact.
    The reason, I wanted to clean up Batch Job History was to improve Performance of the system. 

    Seems like this more house cleaning to get those details..
  • Verified answer
    Hana Xue Profile Picture
    Microsoft Employee on at
    Clean up the batch job history - does not cleanup any jobs from the Batch History
    Hi,
    To view the records of operations performed on the system, you can view through the database log. The official MS doc mentioned that Database logging provides a way to track specific types of changes to the tables and fields in Finance and Operation apps. Changes that can be tracked include insert, update, delete, and rename key operations. When you configure logging for a table or field, a record of every change to that table or field is stored in the database log table, sysdatabaselog, in the environment database.
    For Configuring database logging, you can view the link below:
    Configure database logging - Finance & Operations | Dynamics 365 | Microsoft Learn
    Best Regards,
    Hana
  • Verified answer
    AK2 Profile Picture
    108 on at
    Clean up the batch job history - does not cleanup any jobs from the Batch History
    Hello Hana, Thank you for your response! That definitely helps me understand, why I see Jobs.

    I was also interested in knowing, how we can get the log of all the job history that was deleted?
    Do we need to connect to the database to get a list of the job history? This requirement is more from an audit perspective.
  • Hana Xue Profile Picture
    Microsoft Employee on at
    Clean up the batch job history - does not cleanup any jobs from the Batch History
    Hi,
    The Batch job history clean-up function cleans up the history of job execution, not the job itself. If you want to clean up the job, just click the delete button.


    Best Regards,
    Hana

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Sohaib Cheema Profile Picture

Sohaib Cheema 665 User Group Leader

#2
Martin Dráb Profile Picture

Martin Dráb 595 Most Valuable Professional

#3
Yng Lih Profile Picture

Yng Lih 558

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans