nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Export Features results in consolidation to single location

JasonWeis_Westwood

Since updating ArcGIS Pro to version 3.4.0, when I attempt to export a selection of points collected with Field Maps in an ArcGIS Online hosted feature layer to a file geodatabase feature class, all of the exported points are moved to a single location (the location of one of the exported points). This occurs with both a right-click on the layer name (with Data: Export Features), and also with starting directly from the Export Features geoprocessing tool. The attributes appear to export correctly - it is simply the location of the point that gets modified.

I have been using this workflow frequently in the past (exporting a subset of collected points to a project-specific geodatabase), and the points always exported to the correct location, even if specifying a new coordinate system. This "consolidation" did not occur until I performed the v3.4.0 update. (The display cache was cleared as a troubleshooting step, but had no impact on the error.)

When I tested this with other ArcGIS Online point data that was NOT populated using Field Maps, the points exported correctly. Likewise, when exporting selected points from a local source (file geodatabase), the points also exported correctly. Performing the operation on a workstation with version 3.3.1 did NOT have the same issue - the various points were exported to their proper locations.

Has anyone else encountered this potential bug?

Find more posts tagged with

Accepted answers

JasonWeis_Westwood

From another post: https://community.esri.com/t5/arcgis-pro-questions/problem-exporting-features-from-feature-service-to/m-p/1557374

It sounds like a bug has been logged (BUG-000172816) and is being reviewed by Esri. A temporary workaround seems to involve disabling the export of attachments in the feature layer (Environments / uncheck Maintain Attachments).

Hopefully a 3.4.1 patch will be issued soon, since this is an important part of my workflow.

All comments

GC_GIS

I ended up getting it to work by unchecking "maintain attachments" before exporting.

AJ_Abshire

I still haven't found one unfortunately - I'm still getting this bug.

GC_GIS

Have you figured out a solution to this issue?

luckachi

This issue is still occurring in 3.4.2 however, for me, it has been with polygons. Hopefully 3.5 will address this finally.

FourCornersMapping

This BUG-000172816 is apparently addressed in 3.5, but as of today there are only patches for 3.4 available. The workaround suggested by Esri is to use the Copy Features tool, which maintains attachments.

RobertWagner3

this did not resolve the issue

RobertWagner3

Bad news, even with the patches, it still persists....this is not going to go well if i get a set of points that i cannot practically just manually build from the AGOL layer....

JasonWeis_Westwood

I was hopeful that one of the two patches that became available last week would fix this issue. However, after applying both patches (currently at v. 3.4.2), the issue persists.

TSWCD_GIS

I was lucky enough to have a server machine with a prior version of Pro and everything worked fine. I was pulling data which did have attachments so the work around wouldn't have been helpful in my case, but good to know its an option. Thanks for that update!

JasonWeis_Westwood

From another post: https://community.esri.com/t5/arcgis-pro-questions/problem-exporting-features-from-feature-service-to/m-p/1557374

Hopefully a 3.4.1 patch will be issued soon, since this is an important part of my workflow.

GISAdminSHN

Same issue here

TSWCD_GIS

Dealing with this same bug right now. Trying to back up points and they are all stacked in one location.

JasonWeis_Westwood

I don't have "bug reporting rights" in my organization, so I can't report it directly to Esri. If anyone else experiencing this issue has the capability to submit a ticket, it might be worth letting Esri know about it, since it doesn't seem to be an isolated incident.

Nelmac_GIS

Also experiencing the same issue, as are three other people in my workplace, hopefully they fix this soon as it is annoying.

jcloutier

Hi @JasonWeis_Westwood, 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.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.