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?

[Wolf]

Are you deleting the field using the UI or are you deleting the field programmatically or are you using a Geoprocessing tool?  Can you provide a sample snippet?

[MichaelVolz]

Does this happen to any field or is it more specific to a data type or a field tied to a domain?

[George_Thompson]

What format is the data stored in: shapefile / file geodatabase / enterprise geodatabase / etc. that you are deleting?

[Ed_]

In my experience ArcGIS Pro 3.4 is more stable than 3.3 so maybe start from there?

[MicZatorsky_AEC]

Is it on a network drive?   We have found attempting to rename a field on a FGDB on a Nasuni network drive instantly corrupts the geodatabase while working locally is fine.

[DH_GISP]

We have been looking at Nasuni for a solution. What locking mechanism of Nasuni were you using? (No Locking, Optimized, or Advanced).

[MicZatorsky_AEC]

Sorry, I do not know.

[kntr]

Are you deleting a field from a shapefile or other file-based datasets? Could you export the data into a file geodatabase feature class (.gdb), and try deleting the field again there to see if the issue persist?

Reference: https://pro.arcgis.com/en/pro-app/latest/tool-reference/conversion/feature-class-to-geodatabase.htm 

If this answer solved your question, please mark it as "Accept as Solution" to help others who have the same question.

[HollyTorpey_LSA]

I've never experienced this, but my colleague reported something similar recently after trying to delete a field from the table view. The data in the field he tried to delete turned into wingdings and some of the other fields lost their data (values became nulls): 

In this case, the table in question was the output of a buffer operation, if that makes a difference. It was stored in a file geodatabase on a Nasuni drive and the field he tried to delete was a text field without a domain.