Skip to main content
Solved

Using Audit History in a GI to see if Customer has ever been on Credit Hold

  • April 15, 2026
  • 4 replies
  • 23 views

Hi all,

I’d love to be able to see a widget or GI column that displays historical info about our customers. Specifically, I’d like to see the last time that a Customer’s status was “Credit Hold” and a count of how many times they’ve been on Credit Hold. 

I can’t seem to crack this. I know how to enable field level audit history, and I know the field is Customer.Status. However, I can’t figure out how to display the audit history of this field per customer without digging into the audit history page. 

Thanks in advance,

Nathan

Best answer by BenjaminCrisman

@nathand If going on Credit Hold is any part of a manual process you can have a user defined field that can be increased to keep track of this. Otherwise I think you’d be looking at some very lengthy audit trails which could use a lot of space. Alternatively you could have an automation like a business event trigger when customer goes on credit hold and then perform some action like increase a counter attribute or send an email and then a GI could count those emails.

4 replies

mohammadnawaz51
Jr Varsity II
Forum|alt.badge.img+6

@nathand We can hold only one last audit history only in Acumatica.


BenjaminCrisman
Acumatica Employee
Forum|alt.badge.img+4
  • Acumatica Support Team
  • Answer
  • April 15, 2026

@nathand If going on Credit Hold is any part of a manual process you can have a user defined field that can be increased to keep track of this. Otherwise I think you’d be looking at some very lengthy audit trails which could use a lot of space. Alternatively you could have an automation like a business event trigger when customer goes on credit hold and then perform some action like increase a counter attribute or send an email and then a GI could count those emails.


lauraj46
Captain II
Forum|alt.badge.img+9
  • Captain II
  • April 15, 2026

Hi ​@nathand ,

Unfortunately the AuditHistory DAC is not GI friendly.  All of the field updates are stored in a single field, and the original value is not in the same record.  I once experimented with a SQL view to try to parse the data and use this as the basis for a custom DAC, but it was not very efficient.  I agree with ​@BenjaminCrisman that a business event is the way to go.  


  • Author
  • Freshman I
  • April 15, 2026

Thank you ​@BenjaminCrisman  and ​@lauraj46 ,

I’ll setup a business event and solve it that way. I appreciate the insight on how to work smarter not harder!