We have situations where we need the Parts List item number to be an entered static value. In our assemblies, that part may be referenced in several different subassemblies. Yet, that part in different subassemblies requires having a static value. What we are seeing is that, at times, the subassembly reverts back to all the BOM values, which is what we don't want.
We are not pushing the Parts List back to the BOM, for the reasons stated above, yet we're not sure why sometimes the values stay and other times they revert.
We are also using Vault Pro.
Any info regarding this would be helpful. Thank you!
I'm adding in one more factor, which wasn't previously mentioned. Our IT group has VS running in Vault.
Hi! It is hard to tell what went wrong. By design, the PartsList item numbers should dictate what's shown in the drawing. It can be static. There is indeed an option to push the item number back to the assembly BOM table, so that they are in sync (PartsList vs Assembly BOM).
I guess you don't want them to be in sync. Maybe the so-called "Legacy Structured" or "Legacy Part Only" might be a better fit for you. Have you tried that?
Many thanks!
You are describing it as I've always known it to be. We are not pushing the static value back to the BOM, so that's why this is such an issue. As we are, this becomes hit or miss of when the static value flips back.
Thank you for the suggestion. I'll try it out and post my findings.
I have more info for this issue. Everything is fine until an item is suppressed or unsuppressed within the assembly. And, we've seen something as simple as taking a part off of being referenced to being default in the assembly. Again, part of that I would accept, since the part is now being added and is no longer held as reference.
Hi Jim,
The behavior does not sound right to me. Please share the files with me directly johnson.shiue@autodesk.com. I would like to understand the behavior better.
Many thanks!
Can't find what you're looking for? Ask the community or share your knowledge.