Active Production BOM Version

Alex_Chow
Member Posts: 5,063
Is there a reason why the active version of a particular BOM is not displayed on the production BOM screen?
When I checked the subform linking, it's set to:
If you created a Version Filter flowfilter, you can link the version code to the version Filter. Is there any reason why MSFT did not do this?
When I checked the subform linking, it's set to:
Production BOM No.=FIELD(No.),Version Code=CONST()
If you created a Version Filter flowfilter, you can link the version code to the version Filter. Is there any reason why MSFT did not do this?
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 book
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
0
Comments
-
The Active Version field shown on the Production BOM form is a calculated value. It shows the currently valid BOM Version based on the Staring Date of the version. An active BOM Version must alsohave a status of Certified
The SubFormLink you refer to is as it is because both the Production BOM Lines and Production BOM Version Lines subforms use the same table, Production BOM Line.
So, on the Production BOM form the subform link filters out any lines with a version code, whilst on the Production BOM Version, the subform link filters on lines with a version code.0 -
Umm... I know the programming aspects of it. But thanks for breaking it down.
The question what is the business rule on why it doesn't show the active version on the Production BOM when you pull it up? :?: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 -
Because they're different tables ('Production BOM header' and 'Production BOM Version'). I doubt that there is business logic behind it, I think it has more to do with the way that the manufacturing module was developed, that the version bits were added later, and by that time they didn't want to redesign it.
We've done development where the Production BOM Header form only shows the header record, and you always have to work with Versions for the actual bills of material. Still not something that pops up the active version when the form is opened, but at least the functionality is consistent.0 -
Seems to me just by looking at the code that it's half developed. They're so close to making it work but somehow stopped working on it.
The details is using the same table (Production BOM Line), only the header is using a different table. Since we want the components, we don't really care about the header anyway.
Seems to me all MSFT needed to do was set the filter on the Production BOM Line with the value on the Active Version on the Production BOM Header table.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
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions