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
- 302 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Ledger Entry Pages - sorting set to Entry no.? Why? NAV 2017 and 2018
frededk
Member Posts: 1
Hi,
just wondering - why has this been set on both Cust.ledg. Vend.ledg and Item ledg.entries (Page 38)??
Must give poor performance with many entries?
Best regards,
Henrik
just wondering - why has this been set on both Cust.ledg. Vend.ledg and Item ledg.entries (Page 38)??
Must give poor performance with many entries?
Best regards,
Henrik
0
Answers
Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/
This it is actually attempted and had been working in previous versions, e.g. Customer Card, Action Ledger Entries, using the RunPageView property. Microsoft obviously did not realize, this does no longer work, or did not care, when they decided to sort the page in descending order. With setting the SourceTableView property on the page, this overrides the RunPageView property from the caller.