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
Kit unit of measure
DenSter
Member Posts: 8,305
I am confused... Creating a Production BOM, entering a Production BOM on one of the lines. The validation code populates the unit of measure, but when trying to manually change the unit of measure it says "Type must be 1, 3 or 4 to select a Unit of Measure Code". The message is a text constant (poorly programmed to show the integer value instead of the text value) that seems to have been put in there for kitting purposes.
I can see how for Kitting you don't want to allow a production BOM as a component, but I should be able to enter a BOM with a unit of measure for a regular BOM. Does anyone know what the reasoning behind this is?
I can see how for Kitting you don't want to allow a production BOM as a component, but I should be able to enter a BOM with a unit of measure for a regular BOM. Does anyone know what the reasoning behind this is?
0