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
- 297 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
Posting “Item Reclass. Journal” by NAS.
John
Member Posts: 43
By ADCS we create Item Journal Lines.
If we lookup these Lines in the Item Reclass Journal we can Post them without any Warnings or Errors.
However, if we let the NAS Post this journal we get errors on G/L Accounts with Dimension Code Mandatory.
Can anyone explain the difference and tell me how to avoid the errors?
If we lookup these Lines in the Item Reclass Journal we can Post them without any Warnings or Errors.
However, if we let the NAS Post this journal we get errors on G/L Accounts with Dimension Code Mandatory.
Can anyone explain the difference and tell me how to avoid the errors?
0
Comments
If you post the journal line from NAV and do not run into any issues, I would expect that the code that passes the ItemJnlLine is not working correctly. You should experience the same issue with posting normally in NAV with the client as with NAS.
I have run into this many times and it always comes back to my code...
Let me know if this is not the case.
- Scott
Vice President, Deployment Operations
Symbiant Technologies, Inc.
http://www.symbiantsolutions.com
Thanks