Best Of

I think this is just a geometric issue. If your angle formed a 45° it would be equal, but the more it doesn't the sharper it gets like this. Could you just draw the shape you want from the side view and use Extrude instead?

When editing a sketch, do your best to move objects around. When a line or what ever is deleted and replaced it will get a new ID which will cascade through newer features in the list. Any sketches, extrudes, sweeps etc. can be affected. Faces used for sketch will have a new ID as well.

Had a look at the whole parts studio. I'm not sure why some folks draw sketches out of place and transforms them after. Makes a lot of extra work. Here is a sample showing how much shorter the feature list can be.

I find for me that making sketches in place is less confusing, especially as the project continues.

https://cad.onshape.com/documents/434f9fa2842dfea060196ac6/w/2acc0e7d66e69d2575e53477/e/53b4623666f2948f627cb7e9

PS. I left the fillets out so you'll have something to do. They're B——H

However they can be done on one protrusion and arrayed same as protrusion.

I've done this before, and unfortunately there is no documentation/resources.
My process was to essentially reverse engineer the data structure of a sketch.
Manually make a sketch dimension, and do a "Get Features" api call. Look at what the result is, and then replicate.

Though there are guides published for adding dimensions to drawings here, I can't find any sources for how to add a dimension to a part studio. The closest I've gotten is by creating a BTMSketchConstraint2 with "DISTANCE" as the constraint type. That applies a distance dimension, but I'm struggling to get it to reference sketch features correctly. I've tried creating parameters for a sketch line (BTMSketchCurveSegment155, wrapped in a BTMParameterString149) as well as passing two points (both BTMSketchPoint158 wrapped in a parameter string as well). In both cases the constraint is received but the feature solves with an error complaining that the references didn't resolve correctly.

The best source I've found for adding sketch constraints is the onshape_client package (now archived, though I can't seem to find a superseding repo yet). The tests there successfully apply coincident constraints using the "features" POST api call, which I've replicated. I don't see any information for how to extend this to a dimension however. I'm looking to see if anyone knows of additional guides/examples/documentations, or has the innate knowledge themselves on how to do dimensions. Thanks in advance.

For reference, here is an example of the JSON body code which is successfully received and solved for by Onshape, though producing unresolved errors in the model (passing two points as the parameters, the points were successfully solved for in the model):

{
  'bt_type': 'BTMSketchConstraint-2',

  'constraint_type': 'DISTANCE',

  'driven_dimension': True,

  'entity_id': 'lengthId',

  'parameters': [
    {
      'bt_type': 'BTMParameterString-149',

      'parameter_id': 'localFirst',

      'value': 'myPoint'
    },

    {
      'bt_type': 'BTMParameterString-149',

      'parameter_id': 'localSecond',

      'value': 'my2ndPoint'
    }]
}