Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 385 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Debug without delayed database operations on BC cloud
vaprog
Member Posts: 1,152
I get the error
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
In the case of warehouse receipt, the error is triggered in "Item Tracking Management"(CodeUnit 6500).InitTrackingSpecification line 26 which is
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?
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?
0