Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
BOM Items
I would like to be able to group/configure columns so that items with the same name will show as 1 row and have a multiple number in the quantity column. I realise the the workflow is to only use a single item and duplicate in an assembly but sometimes when there are a few of the same parts in a part studio it can be easier to assemble them by inserting and them grouping them rather than have to use replicate (which is not always appropriate) of copy and mate.
For instances I have been using Igus bearings on a part studio which need to be dotted around the part studio so that the related parts can be drawn. Instead of inserting the bearings where they were drawn and grouping I am inserting one, copying and mating several times or, where appropriate, replicating.
I hope this makes senses!
For instances I have been using Igus bearings on a part studio which need to be dotted around the part studio so that the related parts can be drawn. Instead of inserting the bearings where they were drawn and grouping I am inserting one, copying and mating several times or, where appropriate, replicating.
I hope this makes senses!
0
Comments
Not sure how I can drop parts into an assembly with the same name so they only show in one row in the BOM.
To back up a bit, it sounds like what you're doing is creating multiple bushings in your part studio, and then modeling around them. Then, you when you get to your assembly, do don't want to go through the hassle of placing/mating all of your bushings a second time. This, I think is a fairly common issue with a couple of solutions. (Excuse me, if this assessment is not accurate).
One solution is to use in-context editing, where you have a single bushing model, and insert that same model into the assembly as many times as needed. You can also create a layout sketch to help position the bushings when inserting them into the assembly. Arrange the bushings as necessary, then create an in-context part studio to design parts around them.
Alternatively, you could model a "dummy solid" in your part studio that has your bushing dimensions. Then, you can use the transform tool or Point Pattern feature script to place the dummy model where you want your bushings. Finally, use a boolean operation to subtract the dummy solid from your part. That said, the in-context part studio workflow is probably a little more efficient.
I'm not sure how the in-context would help as it sounds like I still need to insert the bushing into the assembly multiple times. I think I must be misunderstanding your solution. I don't use in-context editing that much as I find it hard to keep track once you have more than one or two contexts to update.
I also can't see how the 'Dummy Solid' would help....perhaps I'm missing the point.
I'll have a look at the learning centre to try and gain some more knowledge.
Thank you for your time and explanation.
I suspect scenarios like your are exactly why in-context editing was added. While part studios can contain multiple parts, they are not designed for creating assemblies and treat each body as being unique, even if the geometry is identical.
The "dummy solid" option is just another way to get the correct bushing geometry into the part studio without actually bringing the bushings into the part studio. I agree with you in that I still don't feel completely comfortable with "in-context" part studios for some reason that I can't quite put my finger on. However, I think they're your best tool in this situation.
Maybe someone else has other options?
The In-context scenario seems hard to keep track of for some reason. When I have tried it in the past things have gone awry because of multiple 'In-context' parts and their corresponding updates. It's fine with just one in-context link though.