Best Of

@Evan_Reese

@NeilCooke asked me to shed some light on this.  Basically, error entities are attached to an id.  If you want error entities to show up, they have to be attached to the top-level feature id.  We do not automatically migrate subfeature/suboperation error entities to the top level feature because that is not always the desired outcome.  Imagine, for instance, calling a Boolean operation in your feature, and, if it fails, catching that failure and instead trying to do that boolean in smaller batches (this is how fix pcb works).  You would not want the error entities from the initial boolean to come through, because that did not cause a feature failure.

The appropriate way to bootstrap error entities from a subfeature to the feature itself is as follows:

try
{
    opFillet(context, subId, ...);
}
catch (error)
{
    processSubfeatureStatus(context, topLevelId, { "subfeatureId" : subId, "propagateErrorDisplay" : true });
    throw error;
}

Or to just pass the top level id directly into the fillet (but, this can only be done for one subfeature, since ids passed into subfeatures must be unique)

To get the nice code box you can click on this button:

and then paste the code from your feature studio into the empty box that shows up.