Skip to main content
Solved

Keep Audit History Function Behavior

  • September 12, 2024
  • 6 replies
  • 60 views

Michaelh
Semi-Pro III
Forum|alt.badge.img+2

How does the “Keep Audit History” under security preferences work exactly? I understand it’s an integer of months, but….

Does it run immediately after saving?

Do I need to optimize the databse or anything to get it to trigger?

I have a LARGE audit history, many many GB and I know that if this triggers it will take a moment. I’d like to be minimally disruptive with my system. How do I use this function properly? How do I know it executed?

Best answer by Michaelh

This function simply “hides” data and does not remove it. You could set it to 24 months, then if you need it to go longer, increase the number of months. 

If you’re looking to save space, you’d need to run a SQL script against the tables who should be truncated to 24 months and ignore the tables who should be longer (or truncate those to whatever the longer period is). 

View original
Did this topic help you find an answer to your question?

6 replies

nhatnghetinh
Captain II
Forum|alt.badge.img+11
  • Captain II
  • 566 replies
  • September 13, 2024

Hi @Michaelh 

According to Acumatica's definition:

“Keep Audit History for

An integer that represents the number of months the system should keep the audit history of user operations.The default value of the box is 999”

 

In Acumatica there are "Access History" and "Audit History" screens. "Keep Audit History" gives you the option to store the audit history of user operations.

Best Regards,

NNT


Michaelh
Semi-Pro III
Forum|alt.badge.img+2
  • Author
  • Semi-Pro III
  • 192 replies
  • September 13, 2024

I know WHAT it does. I want know when it executes.

I have 7 years of audit history, when I choose to keep less than 84 months of history, when will it execute that command? We have a MASSIVE audit history table, if this executes during operating hours, I fear it will create issues for my users.


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2810 replies
  • November 13, 2024

Hi @Michaelh were you able to find a solution? Thank you!


Michaelh
Semi-Pro III
Forum|alt.badge.img+2
  • Author
  • Semi-Pro III
  • 192 replies
  • November 13, 2024

I did not and it appears this function simply hides the data from users and doesn’t actually remove the data, so my Database is still massive.


Forum|alt.badge.img
  • Jr Varsity II
  • 33 replies
  • January 17, 2025

Sorry to hijack the post but mine is set to 999 months also.  i’m thinking of changing mine to 24 months.  i can think of a time when i would want more that 2 years worth of audit history.   does anyone have any suggestions 


Michaelh
Semi-Pro III
Forum|alt.badge.img+2
  • Author
  • Semi-Pro III
  • 192 replies
  • Answer
  • January 20, 2025

This function simply “hides” data and does not remove it. You could set it to 24 months, then if you need it to go longer, increase the number of months. 

If you’re looking to save space, you’d need to run a SQL script against the tables who should be truncated to 24 months and ignore the tables who should be longer (or truncate those to whatever the longer period is). 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings