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
- 304 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
Order dataitem in report
tullio
Member Posts: 39
I've a strange problem.
In a report I need to show progressive customer due balance so, in "Cust. Ledger Entry" OnAfterGetRecord I write ProgrDueBal += RemainingNetAmount;
DataItem "Cust. Ledger Entry" was ordered for SORTING(Customer No.,Open,Positive,Due Date,Currency Code) ORDER(Ascending) WHERE(Open=CONST(Yes))
In the most customer detail all work great but sometime progressive due balance was wrong because printed list detail was different from order that was used in OnAfterGetRecord trigger.
So in my report I'have this list:
Doc Amount Prog. Bal. Due
1 10000 -7800
2 - 1200 -1200
3 - 500 -1700
But debugging code order was different because first was read doc 2, after doc 3 and last doc 1. So Progr. Bal. Due was printed wrong.
Why this??
How I can solve?
In a report I need to show progressive customer due balance so, in "Cust. Ledger Entry" OnAfterGetRecord I write ProgrDueBal += RemainingNetAmount;
DataItem "Cust. Ledger Entry" was ordered for SORTING(Customer No.,Open,Positive,Due Date,Currency Code) ORDER(Ascending) WHERE(Open=CONST(Yes))
In the most customer detail all work great but sometime progressive due balance was wrong because printed list detail was different from order that was used in OnAfterGetRecord trigger.
So in my report I'have this list:
Doc Amount Prog. Bal. Due
1 10000 -7800
2 - 1200 -1200
3 - 500 -1700
But debugging code order was different because first was read doc 2, after doc 3 and last doc 1. So Progr. Bal. Due was printed wrong.
Why this??
How I can solve?
0
Comments