Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit ACU-I-2653 Archiving, Purging and Data Storage Management.

Purge historical data Merged

be able to purge historical data after a given retention time has passed.
  • Guest
  • Nov 3 2014
  • Future consideration
  • Tim Rodman commented
    December 14, 2019 22:49

    See related conversation here: https://www.augforums.com/forums/everything-else/manage-reduce-database-size

    I'd also like to see this functionality become available throughout Acumatica.

    It seems like Acumatica has taken steps in this direction recently with two things:

    1. The ability in 2020 R1 to view deleted transactions in Generic Inquiries.

    2. The Purge Leads and Contacts (CR508000) screen:

    Seems like the plumbing is in place to make this happen on a larger scale in other areas. Maybe start with GLHistory?

    Bonus points if Acumatica could come up with something like a "cold" storage option where you "purge" the data out of the Acumatica database, but into a blob in AWS (especially GL data). Blob storage is so cheap in AWS. And it can still be reported on with BI tools.

  • Ken Hsu commented
    December 06, 2018 06:57

    Please make this coming true because some log tables occupy almost half space on disk. The log tables are AuditHistory, AUScheduleHistory and LoginTrace.

     

    If we don't have this function, we have to ask Acumatica to do that, that is not very reasonable.

  • Guest commented
    January 04, 2016 12:56

    I have a customer that is only three years old, small customer...about 2.5 million per year about 15 orders per day...there DB is over 13gb...that is way too large.

  • Guest commented
    January 04, 2016 12:55

    Some example actions that can be provided.

    Old customers that have not had activity in 1 year

    Clean/archive all tranhistory 2013 and older

    clean all audit history older than 90 days
    clean all old filerevision history older than 1 year
    it can be done, it just needs to be designed
    I'd recommend focusing on the tables that are the biggest first

    Let it be a process screen with actions and filters (to replace my examples) and support Add to schedule