Is it possible to generate a BOM of parts that are shown in a display state?
Ex. I have 100 parts in an assembly. I use a display state to show only the drive components, about 6 parts. When I generate a BOM in a drawing, it shows all 100 parts in that assembly.
Ive tried using configs but it is more work and it seems that after hiding all the parts I do not want to display, I also have to set the "Exclude from bill of materials" in the Component Properties of each hidden part. When you are dealing with a large assembly, this can be a bit cumbersome.
Is this the method you are referring to?
suppress the parts in the config, rather than hide them, and they should automatically be removed from the BOM.
Suppressing certain parts in a major assembly creates havok with mates and parts that rely on those mates.
Chris,
While this thread I am posting is not exactly what you are looking for, it might give you some ideas on how to get there.
hi
This works only if part name is the same as the one used in option bill of material
exaple: prt name: 14-D03-DCM-023-s00-E.SLDPRT
I exported the assembly as step b214
1 - Open the step file as multiple parts.
2 - now you can notice that part name is the same of original part, but these are new parts saved local with the same name but with no properties.
3 - save the (step) newassembly and close it
4 - open the original (your assembly) if don't have it open (resolved)
5 - Open the newassembly: now sw will ask you if want keep the parts already opened. Keep them
now you have a newassembly with original parts. You can then generate the bom.
Hope will help you.
cheers
stefano dolcetti
Hi Chris,
I can feel your pain. I have asked for this function a long time ago. Unfortunately SW has not picked up on it.
It would even help if we could sort the BOM by ballooned items or any other column but at no avail. Man would that make it easy to hide rows.
But again this is not available.
Here is something that can help, but needs work. It will give you a linked BOM without complicating your mates for the sake of BOM functionality.
Got to following link and download macro 19. It's a SW resource site by Stefan Berlitz
SolidWorks MakroMania - Tauschb rse (2)
This macro finds all components that are missing a balloon.
Now here is your task. Look at the code. It already finds all items that are not ballooned. You now need to change it
to hide the rows those items rows in the bom table. Maybe you can do that or maybe someone here can help you with it.
It's beyond my ability but at least it's a good start.
Maybe someone at SW reads this and can see the benefit for us users. Cause BOM's play a big role in Engineering & detailing.
Look at the number of viewers for this thread.....just a hint for SW
Elmar
Create a BOM for your assembly. Select all the rows you want to hide. Click "Hide/Show" on the BOM toolbar.
-Chris S.
Has there been any progress on this issue? We have assemblies with 1000+ subs/parts in them. The detailing drawings can run into 100 pages. We might have a page on a drawing that only calls for 10 parts to be ballooned out to a BOM. At the minute we have to create a BOM table and manually hide all the unused rows. This process causes strain on the computers as well - it can take over a minute to create the table, just to hide most of it again.
We have tried going into really highly organised assembly structures with configurations with display states but this takes even more time to maintain.
All our legacy data is on SolidEdge (the last version we upgraded to was V18 - 2005). This is a screenshot of the BOM insert dialogue:
Here it was simple - you insert the drawing view, pull out the balloons to the items you want to show in BOM and then insert the table, click the option and move on with the rest of your day.
Any functionality of this nature that could be added to SW would literally save weeks of drafting time for my team each year.
Same issue here! if I find something helpfull I will share it!
Just realised this is a 6 year old thread. I have found that setting parts to envelope in selective configurations works pretty well for me. This does not require me to suppress components or delete rows in BOMs, both of which can lead to major problems downstream. However, for large assemblies, setting envelopes can be tedious. What we need is the ability to set envelope inside the configuration table.
You can control it based on configurations, but I do not think it works with display states.