Not sure if this was a fluke or if it's a bug in 3.4, but thought I'd see if anyone else is seeing the same issue.
I have a point feature service with attachments hosted on ArcGIS Online. In Pro 3.4 I selected 10 of the records and attempted to export them to a file geodatabase. All 10 records exported successfully, but all 10 points are now stacked at the location of the last point in the selection.
I had another copy (in a geodatabase) of the same data that I had exported from the feature service prior to the 3.4 update, so I selected the 10 points from that copy and exported them the same way. That export completed normally, and the points all maintained their original locations.
Has anyone else had problems exporting features from a feature service to FGDB in Pro 3.4?
Solved! Go to Solution.
Further update:
A bug has been logged (apparently from another call from someone else... the rep I'm working with found it today). Here's the info:
BUG-000172816: Export Features results in consolidation to single location of point features. [Note: it's happening with polygons too. I haven't tested lines.]
Status: in Review
This bug is logged for the issue that happened after the upgrade to ArcGIS Pro 3.4. While exporting a selection of features collected with Field Maps from an ArcGIS Online hosted feature layer to a file geodatabase feature class, using ArcGIS Pro 3.4, all exported features are shifted to a single location.
Workaround:
The workaround mentioned in this bug is to export in a geodatabase without the attachments enabled (from Data - Export features - Environments - uncheck Maintain Attachments).
[Note: if you need the attachments, use the Feature Class to Geodatabase geoprocessing tool instead.]
This request is currently reviewed by the concerned team, and further action will be taken soon.
This is a known BUG 000172816. The workaround is to use the Copy Features tool, which works as expected and preserves attachments.
I also experience the same issue when exporting data from a selection.
I used select by location to select polygons inside a buffer area, when exporting the new feature all of the polygons export to a single feature (the last one in the selection). The extent in the properties remains as just the one single feature.
Does anyone have a solution?
I have also had this issue since updating to 3.4... A solution I have found is the Copy Features Geoprocessing tool.
Do we know if this bug has been documented on the official Technical Support site?
Hi @HollyTorpey_LSA and @DianaValadares, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.
By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.
As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.
*Note that this is a scripted message prompted when posts allude to a potential product bug.
Thanks, I’m aware but wanted to see if others were experiencing the same thing before going through the time consuming process of a tech support request. Looks like they are.
Unfortunately I’m on jury duty this week, but I’ll file a support request when I get back.
I have not yet received an update on the error, but while testing a bit more I noticed that this stops once we remove the attachments when we export.
It is a temporary work around, but at least you can still export the features to their appropriate location.
@MitchEast @DianaValadares Just an update: I'm still working with Esri support to pin down the cause of the issue (apparently it's not happening to all users, but it is consistently happening for everyone in my organization). The workaround for now is to use the Feature Class to Geodatabase geoprocessing tool instead of right clicking on the layer and selecting Data > Export Features. That tool exports all features correctly.
Further update:
A bug has been logged (apparently from another call from someone else... the rep I'm working with found it today). Here's the info:
BUG-000172816: Export Features results in consolidation to single location of point features. [Note: it's happening with polygons too. I haven't tested lines.]
Status: in Review
This bug is logged for the issue that happened after the upgrade to ArcGIS Pro 3.4. While exporting a selection of features collected with Field Maps from an ArcGIS Online hosted feature layer to a file geodatabase feature class, using ArcGIS Pro 3.4, all exported features are shifted to a single location.
Workaround:
The workaround mentioned in this bug is to export in a geodatabase without the attachments enabled (from Data - Export features - Environments - uncheck Maintain Attachments).
[Note: if you need the attachments, use the Feature Class to Geodatabase geoprocessing tool instead.]
This request is currently reviewed by the concerned team, and further action will be taken soon.
The second workaround did not work for me. It maintained attachments but resulted in the same single geometry.