Define Projection crack-down

[AustinStreetman]

With ArcPro 3.5, ESRI has cracked down on letting us define the projection on a feature class that has a projection. We have been importing an existing schema from an XML and then using Define Projection in a model to redefine the projection for the new project. In 3.5, this no longer works. We tried it in arcPy as well. 

This seems like an unfortunate level of hand-holding. ESRI should trust users to know when it is appropriate to redefine a projection. 

[DavidPike]

Seems like the opposite of an enhancement.  Cui Bono?

[javalos]

I'm having the same issue! Hate that I have to uninstall and go back to 3.4 just to use an out-of-the-box Solution ESRI created themselves for user ease.

[MollyJackson]

After two cases with support services regarding this issue, I've basically been told there's nothing they can do, and I should submit my request to ArcGIS Ideas. So here it is. The more kudos an idea gets, the more visible it is to developers:

https://community.esri.com/t5/arcgis-pro-ideas/allow-define-projection-to-work-like-it-used-to/idi-p...