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.
Is there a way to prohibit including properties for Derived parts at a company level?
Kyler_Walker
Member Posts: 211 PRO
I waste a lot of time removing duplicate names and part numbers from Derived parts that my coworkers have made. We have no use case for having multiple parts with the same name and part number.
Tagged:
0
Answers
No, there is not, but you could always force parts to have a name and part number at the end of your tree: Set Property / Attribute feature
Arena integration has an auto part numbering system I believe.
It sounds like you are using derived improperly. Assemblies handle re-using parts properly. What is your specific scenario?
If you DO want the derived parts to represent the original parts when you put them back into the assembly, you can use the Assembly Imposters (app + feature) to tag and replace parts when they get to the assembly.
.
RENDERCAD
rendercad.ai - Photorealistic product rendering.
▚▞▚▞▚▞▚▞▚
________________________________________________________________________
In my belief, derived parts should never be used in an assembly (with the same part number as the source of the derived part). We tend to use them for reference when we are designing mating parts or as template to which modifications are made to create a new, but similar, part. When inserting a part into an assembly, it's hard to find the real part in a list of derived parts that have the same name and part number as the real one.
This is indeed a challenge. What I like to do if the derive is used for top down design and there’s more details in the derived part is to name the parent like “Part A [parent]” and the real part “Part A”. I also like to name any part which is just for reference (will never be ordered or prototyped) with [ref], and anything which is an import from say industrial design [ID]. The goal is to avoid that confusion of having 17 things all with the same name. I love derive (so much better than insert part in Solidworks), but I do wish that there was a little more guardrails built in to help avoid these opportunities to shoot oneself in the foot.
Simon Gatrall | Product Development, Engineering, Design, Onshape | Ex- IDEO, PCH, Unagi, Carbon | LinkedIn