Exporting feature fails to include all fields

1028
6
Jump to solution
05-21-2024 11:17 AM
MichaelSeymour
Emerging Contributor

I just upgraded to ArcGIS Pro 3.3.0. 

I'm running into an issue exporting features using the typical right click on feature in Contents --> Data--> Export Features. Previously, the output feature would include all the fields from the source feature, but now I'm getting a random assortment of fields that don't include all fields but *do* include previously deleted fields from the source feature...

My workaround is bringing the source feature into ArcMap and exporting the feature that way. It works fine in ArcMap...

Any ideas?

Thanks!

Michael Seymour

mseymour at wlf.la.gov

0 Kudos
1 Solution

Accepted Solutions
DanPatterson
MVP Esteemed Contributor

BUG-000154896 for ArcGIS Pro (esri.com)

apparently, but I don't use your shorcut, but the Featureclass to Featureclass tool (which they recommended as a 'workaround' for some strange reason, instead of the first tool to use)


... sort of retired...

View solution in original post

6 Replies
DanPatterson
MVP Esteemed Contributor

sounds familiar

Solved: Pro not exporting all fields of hosted feature lay... - Esri Community

see if this matches your case


... sort of retired...
0 Kudos
MichaelSeymour
Emerging Contributor

Thanks for the quick reply! Yep, I saw that post, too, but it sounded like the bug had been fixed, no?

0 Kudos
DanPatterson
MVP Esteemed Contributor

BUG-000154896 for ArcGIS Pro (esri.com)

apparently, but I don't use your shorcut, but the Featureclass to Featureclass tool (which they recommended as a 'workaround' for some strange reason, instead of the first tool to use)


... sort of retired...
MichaelSeymour
Emerging Contributor

Yep! That seems to work! Thank you! I really appreciate the assistance!

0 Kudos
JasminePrater
Frequent Contributor

I saw that this bug was fixed in earlier versions of ArcGIS Pro, but we are using 3.3.1 and still encountering the issue.  It's not consistent, but our current workaround is to export the feature to the project geodatabase and then export the table from the new feature.  Both my coworker and I have had the issue over the last two days, but haven't seen it for a month or two before this.  While the issue is infrequent and our workaround acceptable, it still persists in the ArcGIS Pro 3.3.1.

0 Kudos
DanPatterson
MVP Esteemed Contributor

you should report it, they will want to examine data that you are using that throws this error


... sort of retired...
0 Kudos