Deleting Boolean Operations Performed within OGSs

Location of Bodies

When you delete a Boolean operation performed between a body and a body included in an Ordered Geometrical Set (OGS), or performed using volumes, you can choose between deleting aggregated elements or not. You just need to activate or deactivate Delete aggregated elements in the Delete dialog box.

If you do not select Delete aggregated elements, once the deletion is performed, the bodies are located in this way:

  • concerning Boolean operations with volumes:
    • hybrid bodies remain below OGSs
    • non-hybrid bodies are located below the representation.
  • the solid body is always located under the representation

In case you want to keep solid bodies within their OGSs, you need to use the Delete and Keep Operand in Context capability described below.

Delete and Keep Operand in Context

To use Delete and Keep Operand in Context you need to right-click and select the Boolean operation you wish to delete from the specification tree, then select the command thru the contextual menu.

In the example below, Delete and Keep Operand in Context is applied to Assemble.1 is selected. 

Assemble.1 is deleted. Operand Body remains in Ordered Geometrical Set.1.

Insertion of a New OGS

In cases the deletion breaks the sequential construction of the geometry, a warning message is issued, letting you choose between canceling the operation (just click NO from that dialog box) or continuing it (just click YES from that dialog box).  In that particular case, the application inserts a new OGS instead of the Boolean operation.

Initial state

Ordered Geometrical Set. 2 has been inserted after confirming the deletion. The insertion of this OGS is a way of preventing interruptions of the sequential geometry creation.


This capability is not available:

  • For Boolean operations performed with Volumes
  • If the operand body is a solid body. For information, refer to Mixed Boolean Operations.
  • If the second operand is not aggregated by the Boolean operation as illustrated in the following example:

    Initial state

    Body 2 has been added to Body1, but is not located below Add.1 in order to prevent interruptions of the sequential geometry creation. Consequently, Delete and Keep Operand in Context is not available.