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.
Best Of
Re: THE SLOT TOOL IS NOT WORKING AS EXPECTED.
they all look horizontal to me

To draw a slot it is as simple as drawing a line from "center-to-center" of each arc, then select the lines with the slot tool

Re: Creating a drawing from multiple parts
I am a designer and I use OnShape for drawing and planning furniture. My parts are mostly pretty simple rectangular boards–maybe sometimes with a few notches or holes. I also don't need every view (top-view, front and side) because a board just has a thickness and I am interested in showing the length and the height within the drawing.
See my two images what a standard process for me looks like:
1. my parts
2. a drawing I usually end up putting together manually (and this is only a third or so)


So what I would wish for:
- Selecting multiple parts at once to show them in the drawing (if all 3 views would be showed, I would not care)
- Automated labeling of the dimensions, because the labeling is very tedious.
- Option to automatically add the parts name to the drawing. I normally label my parts quite consistently, so that would be great to have the name appearing next to the 2d-drawing.
I also know that I am, like @brett_sutton a free user, but I also believe that this could be a huge improvement!
jones
Re: Multiple derives not allowed?
Funny workaround:
- Go to the part you want to derive twice.
- Go to configuration, and add a new dummy configuration variable. (I made it a text type, but I suspect anything works.)
- You don't have to actually use the variable anywhere :D
- Derive the same part and config twice, except that you give a different value to this new dummy variable.
- You now have two identical parts, but this weird check of disallowing the same config twice thinks the parts are different because of the dummy config variable
I have no clue why this is a limitation. It is definitely not performance:
- I don't see why importing the same config twice is more expensive than importing two different but similar configs
- This can even be an optimization: they have proven to be able to detect duplicate configs, and they can just copy the previously derived part, instead of generating the same config twice
Maybe something weird can happen sometimes if you derive the exact same shape twice. But if so, then this error check fails to prevent that, given the dummy variable trick works.
Does anyone know why this is a limitation, or can the devs just remove this limitation maybe?
Re: BOXed-In, Branch-Out?
To be clear, you don't need to "know" anything to use FeatureScripts (other to know where to find the ones you need, which is a whole topic by itself)!
Just open the document containing the FS (eg the links provided above) and click the "+ Custom features" button at the top and click on the FS to add to your toolbar, then it's just like any other "regular" feature.
Re: BOXed-In, Branch-Out?
Also, here's an example of how the "properties/attributes" work:
I added a configured " part color feature" as well after recording:
Re: BOXed-In, Branch-Out?
@brandon_nichols678 , the "name" column in the configuration is the name of the configuration itself. The "name" column is the configured properties is the name of the part. The difference becomes more obvious when you have more than one configuration input (something that doesn't exist in SW), not sure if you've used that yet… The configured properties will have a column for each configuration input on the left so that each line in the configured properties describes one combination of configuration inputs.
I second @MichaelPascoe 's comment to use the property/attribute FS (and configured text variables) to build the names. The "variable to string" FS is also helpful for this:
I would also highly recommend using the "part color" FS as it is easier to manage than through configured properties:
One last thing to be aware if you go this way is that you will need to "rest all" (in the properties) for the property/attribute and color FS to take effect if you have manually set part names and appearances.






