Autodesk Vault Professional - BOM Row Property Behavior Feedback
Subject: Usability Concern: Non-Mapped BOM Row Property Propagation
To: Autodesk Vault Product Development Team
We are experiencing unexpected propagation with non-mapped BOM Row Properties in Autodesk Vault Professional.
Problem: When a BOM Row Property (e.g., "Specific_Attribute") on a "grandchild" component (C) is modified within the BOM of a "grandparent" item (A) – where C is nested under a "parent" item (B) – the modification propagates. Instead of remaining unique to A's BOM, the change is applied to B's internal BOM definition. Consequently, if B is used in other "grandparent" BOMs (A'), they also reflect this unintended change.
Example: Modifying Specific_Attribute for C in A's BOM leads to B's internal BOM being updated. This change then appears in A''s BOM, if A' also uses B.
Impact: This behavior significantly limits our ability to manage item variations specific to a higher-level assembly without duplicating "parent" items. It increases complexity and can lead to data management challenges.
Request: We request a mechanism to define and modify BOM Row Properties that are truly unique to the specific instance within the highest-level BOM, without altering the master BOM definition of intermediate sub-assemblies. This would greatly enhance flexibility and usability for complex product data.
