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.
opBoolean UNIONs
robert_carpenter114
Member Posts: 8 ✭✭
For anyone having difficulties with opBoolean unions, I discovered that adding
"targetsAndToolsNeedGrouping" : true to the parameters list
caused the operation to be performed successfully.
opBoolean(context, getUID(id, "boolean", 2), {
"targetsAndToolsNeedGrouping" : true to the parameters list
caused the operation to be performed successfully.
opBoolean(context, getUID(id, "boolean", 2), {
"tools" : qCreatedBy(getUID(id, "extrude", 2), EntityType.BODY),
"targets" : partToADDto,
"operationType" : BooleanOperationType.UNION,
"targetsAndToolsNeedGrouping" : true
});
Tagged:
2
Comments
It is because, when you don't have "targetsAndToolsNeedGrouping" : true, it only uses the tools, not the targets. It is link the normal Boolean feature
IR for AS/NZS 1100
The preferred way to do a simple boolean union is to put all the bodies to merge into the "tools" field. You can do this by combining multiple queries with qUnion.
<div>opBoolean(context, id + "boolean1", { "tools" : qUnion([ firstEntities, secondEntities ]), "operationType" : BooleanOperationType.UNION });<br></div>THANK YOU, THANK YOU, THANK YOU. After days of fighting issues, recruiting AI's (claude, GPT5) and literal countless attempts, your solution to add that one line resolved all my issues. God bless you for posting your finding.