To whom it may concern
A recent update for ArcGIS Pro 2.5.0 and ArcPY will cause serious issues to features and shapefiles.
While testing some code I wrote between myself and our GIS analyst, I found something very odd occurring with the following sample code snipet.
arcpy.management.CalculateField(currentFeature, "DesiredFieldName", "'New Text'", "PYTHON3", '')
In ArcGIS 2.4.2 this code snippet fails if "DesiredFieldName" does not exist in the table of currentFeature. This is normal and should occur ensuring that currentFeature is indeed properly formated and that "DesiredFieldName" is indeed within the feature.
However, in ArcGIS Pro 2.5.0 this code adds the field
