Debug without delayed database operations on BC cloud

vaprog
vaprog Member Posts: 1,162
edited 2025-03-27 in NAV Three Tier
I get the error
The record in table Whse. Item Tracking Line already exists. Identification fields and values: Entry No.='69038'

I get this rather often, but it is not reproducible. I get it for different kind of operations, related to warehouse receipt, warehouse shipment and pick.

I have error call stacks for the case of warehouse receipt and warehouse shipment

In the case of warehouse shipment, the error is triggered in "Item Tracking Management"(CodeUnit 6500).DeleteWhseItemTrkgLinesWithRunDeleteTrigger line 12 which is 
if WhseItemTrkgLine.FindSet() then

In the case of warehouse receipt, the error is triggered in "Item Tracking Management"(CodeUnit 6500).InitTrackingSpecification line 26 which is 
if WhseItemTrackingLine.FindSet() and not IsHandled then begin

Obviously, the error is not caused there. It looks like the faulty insert was cached before, and now the table has to be read, the system needs to flush the cache first.
On Premise there are settings in the middle tier to do database operations immediately.

Is there any way to find the faulty insert on cloud?

Categories