Small bug in CU90 in Nav 5 - solution
imurphy
Member Posts: 308
I recently came across an error at a clients. When you create a purchase invoice and import lines from delivery receipts you can get an error due to a mismatch in field sizes.
The error occurs in CU90 line 3004. Its a subroutine which contains a line
I don't know if there is a Kb on the subject or not but the solution is simple.
Ian
The error occurs in CU90 line 3004. Its a subroutine which contains a line
OrderNo := PurchRecptLine."Order No.";The problem is that "Order No." is 20 chars long and OrderNo, a local variable, is only 10. Obviously, you need to modify the local variable and increase it to 20 as well.
I don't know if there is a Kb on the subject or not but the solution is simple.
Ian
0
Comments
-
What version is this?David Singleton0
-
It is still there means 2009 too has it. But thanx for the update man.Kapil Khanna0
-
imurphy wrote:I recently came across an error at a clients. When you create a purchase invoice and import lines from delivery receipts you can get an error due to a mismatch in field sizes.
The error occurs in CU90 line 3004. Its a subroutine which contains a lineOrderNo := PurchRecptLine."Order No.";
The problem is that "Order No." is 20 chars long and OrderNo, a local variable, is only 10. Obviously, you need to modify the local variable and increase it to 20 as well.
I don't know if there is a Kb on the subject or not but the solution is simple.
Ian
Confirmed on Nav2009
On Function
TestGetRcptPPmtAmtToDeduct(PurchHeader : Record "Purchase Header";PurchLine : Record "Purchase Line")
MatteoReno Sistemi Navision Developer0 -
This error should be reported to Microsoft via customersource or partnersource.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
I found this on a client who I upgraded to Nav 5.0 sp1. The line doesn't seem to be present in pre-sp1 code which we are still using internally so I assume this is a bug introduced in the service pack.
Ian0 -
This has been fixed in 2009 Sp1.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions

