Data Corrupts when deleting field

[JamesPoeschel]

(ArcGIS PRO 3.3.0) 

Whenever I delete a field from the table view I have an 80% chance of corrupting the file, if I delete a field from the fields views its more like 40%. I've corrupted so much data this past year. Why is it so easy to corrupt data in ArcPRO? It wasn't like this in 2.x or even 3.1. Does anyone else run into this?

[sfmcats]

I had this same issue with 2 different files. The data were corrupted in other fields of the feature class (i.e. the fields I was trying to delete did delete and the data that was corrupted was in other fields) turned into wingdings or other unintelligible text. One instance was in deleting fields in the table view and the other instance was in deleting multiple fields with the geoprocessing tool ‘delete field.’ Both data were feature classes stored in separate file geodatabases. I am using ArcGIS Pro 3.5.2. Both were on my C drive. Field types that were deleted varied – text, short, long, etc. Does anyone have any solutions for this problem? Thanks!

[MicZatorsky_AEC]

Where was the GDB, local or network?

[Wolf]

From previous posts I guess that data is local and not network related.  I am trying to duplicate this issue (programmatically) right now.

[Wolf]

@HollyTorpey_LSA   can you please send me the County feature class / table from your colleagues (you showed the screen shot with wingding corruption above) ?   you can use the 'private message' icon (mail) on the top right of this screen to send me a zipped attachment.    I tried to duplicate the problem programmatically, but it is working properly in my tests so far.   Also, what are using to delete the field?   GP Tool or DDL API?   Finally, when you delete the field is the deleted field in the middle of your attribute columns schema or at the end?  If possible i would like to get the 'good' and if you still have it the 'corrupted' data as well.

[JoshuaBixby]

Are the data sources stored locally on your computer or a shared network drive?

[JamesPoeschel]

Thanks for all the replies, I didn't see a notification so I forgot about this. 

I updated to 3.5 and I still often get this issue if I delete fields in the table view in PRO. Though it almost never gets corrupt if I delete fields in the field view instead of table view, so I generally just do that now even though its an extra step to open up the fields. 

Data is always in a file gdb and always on a shared network drive. I've gotten the wingdings many times as well which is the worst since the data is really corrupt at that point but most often PRO just crashes and I just have to reopen. 

Do you all think the fact that we do everything on a shared network drive is the culprit? I put pro projects and gdbs in a shared drive that follows GIS naming conventions.