Best Of

Do you need the MC in the final feature? You could just apply the transform to upperMC cSys, then use plane(cSys).

Otherwise, try:

var newSketchMC = evMateConnector(context, {
                "mateConnector" : qCreatedBy(id + "mateConnector1", EntityType.BODY)
            });


        const sketchUpperID = id + "upperBore";
        const upperBore = newSketchOnPlane(context, id + "sketch1", {
                    "sketchPlane" : plane(newSketchMC)
                });

This is my biggest misgiving with using community featurescripts for commercial work. Sure it's nice that something exists, but reliability is essential for commercial applications and I'd really rather Onshape provide the tools I need to do my work, rather than tools I can use to make the tools I need to do my work, particularly for basics like threads.

Onshape really needs to provide the functionality themselves so it comes with the assurance of stability and bug fixes - particularly as other updates are rolled out regularly to onshape.

I'm pretty sure there's a deliberate avoidance of any functionality that could make a part regenerate differently with the exact same inputs, so I don't expect you'll ever have this as a live thing, but I could imagine it as a "click to update" kind of situation. Best I've got for now is to make a variable feature with a string of the date and update that manually. It would at least populate to all of the places it's used in that model. There is likely also a way to do it via the API, but I don't know enough about that.