Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K 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
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 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
COMMIT in Hotfix 8 MBS 3.70
remcovanh
Member Posts: 8
In hotfix 8 MBS 3.70 are some COMMIT-statements added.
In Codeunit 5763 and in report 5763.
In Codeunit 5763 first the salesline and salesheader are updated, after that you find the COMMIT-statement and after that the salesorder will be posted by codeunit 80. If an error occures in Codeunit 80 there is no commit rollback. For instands if you have a shipment that has to be deliverd completely. This check is in codeunit 80. When the error occures the fields qty to ship and qty to invoice are already commited.
Same problem in report 5763. In the functions CreateShptHeader and CreateReceiptHeader are also COMMIT-statements added.
If you create a shipment the first time it is OK. If you open the salesorder enter an extra item, release the salesorder and create a shipment for the extra item it creates 2 new shipments. In with the item and one with only a shipmentheader.
What is the purpose of these extra COMMIT-statements??????
In Codeunit 5763 and in report 5763.
In Codeunit 5763 first the salesline and salesheader are updated, after that you find the COMMIT-statement and after that the salesorder will be posted by codeunit 80. If an error occures in Codeunit 80 there is no commit rollback. For instands if you have a shipment that has to be deliverd completely. This check is in codeunit 80. When the error occures the fields qty to ship and qty to invoice are already commited.
Same problem in report 5763. In the functions CreateShptHeader and CreateReceiptHeader are also COMMIT-statements added.
If you create a shipment the first time it is OK. If you open the salesorder enter an extra item, release the salesorder and create a shipment for the extra item it creates 2 new shipments. In with the item and one with only a shipmentheader.
What is the purpose of these extra COMMIT-statements??????
0