Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K 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
- 298 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
Aged Accounts Receivable report
afarr
Member Posts: 287
We have a client who has problems with the Aged Accounts Receivable report (i.e. report 120).
Some background
I have had a look at some 5 different threads on this site that deal with this report (I think that it used to be report 10040), and it seems that it had its fair share of problems.
The Nav 4 report seems to have many changes from the 3.70 report, and one person reported that the 4.02 report had a bug that was not present in 4.01 or 4.03.
The Nav 5.0 report is the same as in Nav 4.03.
Our client is using a modified version of the 4.01 report.
Question 1.
The previous report had many CALCFIELDS, but the 4.01 report has only a single CALCFIELDS (for the Remaining Amt. (LCY) field). The report does use other FlowFields, such as Amount and Remaining Amount. Is there any reason why they are no longer calculated?
Question 2.
When Aging By Posting Date, the report (both in Nav 4 and Nav 5) executes the following code in OpenCustLedgEntry data item:
I have made this code execute even when aging by Due Date or Document Date, and this solved an error that the client had encountered (some entries were showing even though they had been closed).
It seems strange that this code was not changed from Nav 4 to Nav 5. Have you encountered this error? Did you fix it the same way that I did?
Thank you,
Alastair
Some background
I have had a look at some 5 different threads on this site that deal with this report (I think that it used to be report 10040), and it seems that it had its fair share of problems.
The Nav 4 report seems to have many changes from the 3.70 report, and one person reported that the 4.02 report had a bug that was not present in 4.01 or 4.03.
The Nav 5.0 report is the same as in Nav 4.03.
Our client is using a modified version of the 4.01 report.
Question 1.
The previous report had many CALCFIELDS, but the 4.01 report has only a single CALCFIELDS (for the Remaining Amt. (LCY) field). The report does use other FlowFields, such as Amount and Remaining Amount. Is there any reason why they are no longer calculated?
Question 2.
When Aging By Posting Date, the report (both in Nav 4 and Nav 5) executes the following code in OpenCustLedgEntry data item:
CALCFIELDS("Remaining Amt. (LCY)");
IF "Remaining Amt. (LCY)" = 0 THEN
CurrReport.SKIP;
I have made this code execute even when aging by Due Date or Document Date, and this solved an error that the client had encountered (some entries were showing even though they had been closed).
It seems strange that this code was not changed from Nav 4 to Nav 5. Have you encountered this error? Did you fix it the same way that I did?
Thank you,
Alastair
Alastair Farrugia
0