Skip to main content
Solved

Are there any guidelines/recommendations about adding custom DB Triggers to Acumatica tables?

  • 6 August 2024
  • 1 reply
  • 22 views

Hi All,

Are there any guidelines/recommendations around custom DB Triggers in Acumatica tables that would help me assess whether it is a good or bad idea to add them?

I have another team at my company that develops custom web application that integrates with Acumatica.

They need fast sync of data from and to Acumatica, and they have already built a process that relies on LastModifiedDateTime of a record (such as SOOrder, SOShipment, InventoryItem, etc).

What they don't like is that LastModifiedDateTime seems to be calculated by the code, not assigned by SQL, and this makes rear cases when record updated later can get LastModifiedDateTime which is not the most recent one.

To "overcome" this issue they want to add new custom DateTime fields in Acumatica tables and add triggers that will populate them as soon as update/insert has happened.

I’m looking to hear from community about pros and cons of this type of changes

Best regards,

Andrey

In general adding custom DB Triggers is not recommended. 

It’s not clear how they will be processed by a DB upgrade procedure. 


Reply