I am having issues trying to run an Export Data from a Feature Layer (hosted) on ArcGIS Online to a FGDB. This particular Feature Layer contains 2 related records tables and also an ATTACH table (with pictures). This however, is the same type of configuration I have setup for 5 other hosted feature layers that export to FGDB without a problem. When it fails, all that I see is a popup with a header of Error, and a message of failed. (attached)
The only way I can seem to back this particular Feature Layer up is when I do an Export to GeoPackage. (GeoPackage is the only other one that seems to maintain the related record and attach tables)
I would really like to be able to push this hosted feature layer to FGDB. Has anyone had any experience with this occurring to them? If so, what did you find to be the problem as to why you couldn't push to FGDB.
Thanks,
Matt
How did you create the layer?
At a glance it sounds like something invalid in there. Could be anything. You'd have to share more about the data or try monitoring web traffic to pick up the job request.
Can you run feature class exports in ArcGIS Pro with maintain attachments set in the environments?
Thank you for responding, I hadn't thought to try that route via ArcGIS Pro. I gave it a try, and unfortunately it appears that I cannot add the Feature Layer at the top level, to the Export Features tool. If I add the actual feature from within the hosted Feature Layer and keep 'maintain attachments' checked, it does export the feature class and maintains the ATTACH table that houses the photos, but the process drops the 2 related record tables.
The feature initially came from ArcGIS Pro, and was published to ArcGIS Online. After it was pushed to ArcGIS Online, a handful of schema changes were made to the feature within the hosted Feature Layer. The hosted Feature Layer still behaves as expected when consumed in our Field Maps application, but I agree that something must have gotten changed that ArcGIS Online is now not happy with. Also, it is hard to troubleshoot the problem when all I am getting is 'Error - failed' as an error message.
This old Esri Community post and its different replies might be of help.