Does anyone know a way to link a single BOM table to multiple views from different assemblies ?
Start a new Assembly and insert both of those assemblies into it. Save it and insert a drawing view of the new assembly. Insert a BOM. Hide (or delete) the drawing view of the new assembly. Link your drawing views to the BOM and add balloons as needed.
Thanks for your reply Glenn !
I thought that would exist a way with the assemblies separated, but this idea can solve my problem for now !
To me it looks like the same assembly with two configurations. Is it true?
For this case I could make a single assembly with two configurations, but I asked thinking in a generic case when i have different items.
Emilio Janssen wrote: ...but I asked thinking in a generic case when i have different items.
Emilio Janssen wrote:
...but I asked thinking in a generic case when i have different items.
Then my suggestion should work for you.,
Here is a slight variation to Glenn's solution. Let's say you have a large assembly. Sometimes you need to itemize and call out information for only a few parts like in your case support components for a pressure vessel. Similar to Glenn's suggestion, make a new assembly but instead of inserting sub assemblies, only insert the components that you want to itemize. Then insert this dummy assembly & BOM in the drawing and link all corresponding views to this BOM.
While I wouldn't do that if I need to call out the proper quantity (error prone). However this technique works well to call out part numbers, meta data & balloon specific items. In essence it's a workaround for SW missing capability to filter BOM for ballooned items only (hint 2099 maybe).
To make file management easier, I sometimes create a special configuration i.e. BOM-01 with the name indicating that it is merely a place holder. I usually insert all components into a folder inside the Feature manager and make sure this folder is suppressed in all other configurations except the BOM-01 (otherwise it can obviously mess up your true quantity count).
That way I don't need a separate assembly.
Hope that helps
Nice tip ! Didn't thought about that, thanks for you advice, in future will help !
Retrieving data ...