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
- 310 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
Missing Error messages when post Warehouse receipt
Tadeus
Member Posts: 2
If the reciept have some kind of error,
When I try to post receipt in WMS, the message that the system shows for example is "Number of source documents posted: 0 out of...”
OK but there is no way to understand what errors occur during the posting process
And this is terrible.
For some reason the system do not show the error messages in the code units.
I see the options in WMS setup "Receipt posting policy" but it seems not working, there is no diferrence what i choose there.
Please help!
When I try to post receipt in WMS, the message that the system shows for example is "Number of source documents posted: 0 out of...”
OK but there is no way to understand what errors occur during the posting process
And this is terrible.
For some reason the system do not show the error messages in the code units.
I see the options in WMS setup "Receipt posting policy" but it seems not working, there is no diferrence what i choose there.
Please help!
0
Comments
:?:
Lead Consultant
Theta
The response from Microsoft Support is:
It is actually a workaround because the IF SalesPost.Run THEN could lead to inconsistent data and has been changed to the same code as if the parameter has been set to Stop and show the first posting error. As soon as there is a good solution to get around the posting errors and also guarantee consistent data at the same time, the code will be implemented here again.