Can't add fields to service with related table. Is this expected behavior? Workaround?

[SFM_TravisBott]

I cannot seem to add a new field to a related table in a feature service. Is this expected behavior?

Below is the GUI option for a regular service without related tables....

And below is in my service with related tables...

I've checked a few other services and it seems this is consistent. So the question: is there a recommended workaround? I have already created several dependent products off this data and I would really like to avoid republishing. Can fields be added in Pro? Vis the JSON at the REST endpoint?

There is currently a view created from a join, so that may complicate things, but I'm familiar with the workflow for adding a field to a parent service and editing the JSON to let it trickle through to the view. 

[BillFox]

I think we are not allowed to change our minds after publishing.

[SFM_TravisBott]

Except you can! Just not with a related table. And not easily with a view.