How to handle deletes in Acumatica

Question

For building an ETL pipeline to warehouse Acumatica data, are there any approaches to detect deleted records besides the traditional primary key comparison method?

stephenbologna39 · Accepted Answer

Hi ​@PradheepPrabhakaranIf you are using Acumatica 2025 R1 or later, you could try the following (see the section on ‘Tracking Removed Records for Synchronization’):https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=27f3a57a-0def-48ad-ba80-3ab664a98fdeThis will only return the NoteID field for each deleted record though.If you need something more real-time rather than on demand, you could also try Push Notifications:https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=d8d2835f-5450-4b83-852e-dbadd76a5af8

harutyungevorgyan · Answer

Hi ​@PradheepPrabhakaran,There is no single mechanism that covers every table.Detection options (choose by version and table):Tracked removed records (2025 R1+). As @stephenbologna39 said, this returns only the NoteID of each deleted record. Key your warehouse rows on NoteID for the tables where you use it.Preserved deleted records. For tables that keep theDeletedDatabaseRecordsoft-delete flag (or where you add the soft-delete column through a customisation), a GI with Show Deleted Records can return them. DAC-based OData v4 filters them out. Deleted rows then stay in the table, so check for table growth.Push notifications per entity GI. A delete shows up as a row in Deleted that has no matching key in Inserted within the same message. Write those rows to a tombstone staging table. De-duplicate on the message Id. Failed messages are kept for only two days, so this layer needs the reconciliation below.Your own tombstone table. This is version-independent and works for any graph that deletes through the cache. Attach an attribute to the entity's NoteID through a DAC extension with [PXMergeAttributes], and expose the log table through OData.

Sign up

Social Login

Login to the community

Social Login