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.
Configurable Variable in Part Name
sam_ettinger011
Member Posts: 5 PRO
I have a part that uses configuration variables (an extrusion length for 8020) and I would like the part name to update with the variable length in it. Does this feature script exist? I found a feature script for "part number", but haven't found one for "part name".
0
Comments
https://forum.onshape.com/discussion/13832/configure-part-name-feature
Learn more about the Gospel of Christ ( Here )
CADSharp - We make custom features and integrated Onshape apps! Learn How to FeatureScript Here 🔴
https://cad.onshape.com/documents/f4d470584fdeef9603415532/v/be3811a14225d4487f9a3eb5/e/acddbbed81af3772a07adf21
Learn more about the Gospel of Christ ( Here )
CADSharp - We make custom features and integrated Onshape apps! Learn How to FeatureScript Here 🔴
Did you get this working? I too want 8020 lengths in an assembly BOM. I'm not sure feature script will do it since it's stuck in a partstudio. I was hoping for something in an assembly that can interpret various instances in the assembly and tell me a config value based on an instance and then have it show up in the BOM.
I have an assembly with several... several (>100) configuration combinations. I was hoping to build a smart string for the part number based on the configuration parameters but I am struggling to figure something out. As of right now, for my assembly, the only way I know how to populate all of the part numbers is to hard code them for each configuration. I need to do this because when exporting these assemblies to a PLM (e.g. Duro), I want the PLM to catch that the part already exists and not have someone create a new part number for an existing assembly.
To me, this is the single most important reason of being able to build a smart string in the part number field of an assembly.
cc: @alan_baljeu