Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Locking/Blocking/Concurrency
monoxonox
Member Posts: 4
Hi,
could someone please briefly explain the idea behind this line in Codeunit 80 (NAV 2013):
I understand it has to do with locking/blocking and concurrency, but I would like to understand this a bit better. Has this function/line been added to prevent DEADLOCKS, i.e. does this correspond to the changed locking in this codeunit?
Thanks for your replies!
could someone please briefly explain the idea behind this line in Codeunit 80 (NAV 2013):
SortLines(SalesLine);
I understand it has to do with locking/blocking and concurrency, but I would like to understand this a bit better. Has this function/line been added to prevent DEADLOCKS, i.e. does this correspond to the changed locking in this codeunit?
Thanks for your replies!
0
Comments
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
I am interested in understanding the benefit of this change. Maybe you could elaborate a bit more?
Thank you!
http://blogs.msdn.com/b/nav/archive/201 ... -2013.aspx
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n