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
- 305 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
How to input Quantity in SO, Type=G/L
nikeman77
Member Posts: 517
Hi guys,
does anyone knows how to input quantity in so, type=g/l ? i saw in my live db there's a lot of posted sales invoice with type g/l, quantity >1.
but when i tried it in test db, it says: Item No. XXX does not exist.
does anyone knows how to input quantity in so, type=g/l ? i saw in my live db there's a lot of posted sales invoice with type g/l, quantity >1.
but when i tried it in test db, it says: Item No. XXX does not exist.
0
Answers
It sounds as if your testdb is customized. In a CRONUS demo database this shouldn't happen... It is normal to enter SO lines with quantity.
with best regards
Jens
---
I am here: http://maps.google.com/maps?ll=52.524393,13.366335
Check with debugger where exactly it is showing error
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
please ignore this post, just some modification done that i wasnt aware of only..
If the type is g/l account, the error message should not be 'item No. XXC does not exist'.
CouberPu
thanks for replying, it was my mistake. i didnt realized currently there is a customization done (not by me certainly!) and the :bug: bug wasn't fixed yet. it seems a little misunderstanding here. my apology.