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: qCreatedBy doesn't work for boolean operation

you should look at the documentation for opBoolean itself:

BooleanOperationType.UNION will merge any tool bodies that intersect or abut. All tool bodies have to be of the same type (solid or surface). When operating on surfaces, surfaces must have coincident or overlapping edges. When several bodies merge, the identity of the tool that appears earliest in the query is preserved (in particular, body color and body name are taken from it).

so if you have something like that:

const toolsQuery= …;

const firstMergedBody = toolQuery→qNthElement(0);

const mergedBodiesFromFaces = evaluateQuery(context, toolsQuery)→qUnion()→qOwnedByBody(EntityType.FACE)→qOwnerBody();

opBoolean(context, id +"merge", {

operationType:BooleanOperationType.UNION,

tools: toolsQuery

});

then after boolean operation firstMergedBody query should resolve to first resulting body - if you are sure that this is the only body then you are good, if you can expect multiple merged bodies after boolean - you need some another approach -for example you can track bodies by their faces because surprisingly faces queries are more stable through boolean operation from my experience so mergedBodiesFromFaces should do the work as well.

These are the generic approaches, not specific to any query types, because some types of queries can perform better than others in this circumstances and might not require that kind of trickery.

Konst_Sh

Re: Can anyone show me how to properly use opLoft Connections?

I decided to simplify the attempt a bit and it looks like I just needed to get the syntax right. I'm not 100% sure why it didn't work last night. It looks like I needed a connection map per edge section, and not per loft profile. As such, this ended up being the correct syntax:
var connectionMap = {"connectionEntities" : qUnion([vertex1, edge21]),"connectionEdges" : [edge21],"connectionEdgeParameters" : [0.5]};

I still need to implement the connections for when side 2 is a split number of edges, but hopefully that's not too bad. I did end up using evDistance and evEdgeTangentLineand those seemed to work out just fine. I'll keep the other method in my back pocket since it might be cleaner since you're just dealing with edge parameters on both ends.

ry_gb

Custom Feature: Keep Part

-Link to feature up front-

I can't believe I never posted about this one.
You guys know Delete Part? This feature is nothing like that.

Use it on really gross imports with a billion objects you don't care about. Probably don't use it for any other reason.

Derek_Van_Allen_BD

Re: Improvements to Onshape - December 12, 2025

Huge number of fixes in this one! love to see the consistency!
Merry Christmas Onshape crew. You've done amazing. I hope we can make you proud with how we use it next year

christopher_dziuba

Re: Custom Feature Part Name (Ovyl)

This is a very useful feature, thank you!

Would you add a note, that this FS only works on parts that hasn't been renamed manually. If a part was renamed manually, user must use Reset ALL button in part's properties, which is a bummer…