Error 002809 Field OID unsupported in shapefile export

[AndrewFletcherWTS]

I am using ArcGIS Pro 3.2 and have come across the Error 002809: FIeld OID in xyz is of an unsupported type for the output workspace. I have not been able to find this error in ESRI resources or community chat. It seems like an obvious problem that should not exist given the limited options for export from the geodatabase in Catalog. The geodatabase requires the OID and fails to export as FID or appropriate for shapefile. Any ideas gratefully appreciated.

[WindsorConnecticut]

I've tried all of these work arounds and still have an error. I export this exact shapefile on a monthly basis and I've never had a problem until now. This seems like it must be some type of bug with the newest updates from 3.2.2 or 3.2.1... Can we get an ESRI rep in the chat please???

[konsta_kuorikoski]

This is really odd issue. Nothing so far said here was working. Its almost like having "Big Interger" there from start taints data somehow. I tried to export in project geodatabase, then export again as shapefile. Then manually adding field to Big Integer values and copying them to text field, then removing this supposedly problematic field. This did not work, as I could also read from this thread.

Workaround was to open same geodatabase in QGIS and export to shapefile with that. Looking at field types, QGIS automatically converts field type to Double.

[DanHardwick]

I have also ran into this problem, and I think one solution is to go into ArcGIS Pro 'Options' and within 'Map and Scene' enable "Use field types that are compatible with ArcGIS Pro 3.1 and earlier...". 

Then create a new geodatabase and import your data, it should now allow you to export the data to shapefile. 

[KejiLi]

I tried, it didn't work......

[WindsorConnecticut]

I ran into this same issue. I have another computer with an older version of ArcPro, 2.9.1, and this was my workaround until this is resolved. 

I have another issue when publishing this layer to my enterprise, which is 10.9.1. I used the same work around of using the older version of ArcPro and I did not have an issue. If this works in 2.9.1 but not the most recent update, it sounds like this is an ESRI issue/bug they need to address. 

[KFung_TLC]

Still no solutions in sight? I post on this thread last year, & now I need to export features to shapefile & the same error occurred again?

My job needs constantly provide data to municipalities or other agencies, which shapefiles remain the most common type. But everytime I attempt to export from features to shapefiles this bugs me, and they never provide us WHICH field(s) has the problems. For the records, I checked my features in question is 32 bit ObjectID. 

Com'on how can this problem remain for so long. 

UPDATE: Fortunately I checked the attribute table again (Parcel data in question) & the only one field has the issue is regarding the "Date only". So I change that field from "Date only" to "Date" following the solution I found via here:

https://support.esri.com/en-us/knowledge-base/error-arcgis-pro-002809-field-name-in-location-is-of-a...

Hopefully that annoying bugs can be resolved for good.

[ConCon]

Still having this issue in ArcGIS Pro 3.4.2 and checking the box in the Map and Scene in options does not allow me to export to a shapefile.  I had to copy the data and delete the Big Integer fields.  This is not ideal when I am trying to export a live feature service.

[WindsorConnecticut]

The solution I’ve been using is to change the field type from “Date Only” to “Date” when you’re going to export the file. Expand the “Fields” dropdown and find the problematic columns. It doesn’t change anything in the output really. I’m sure there’s some catch with this one but it’s been working for my use.