Anhänge in AGOL Feature Service schreiben

Question

Ich frage mich, ob jemand Erfolg hatte, Anhänge in einen bestehenden Feature Service zu schreiben, der auf ArcGIS Online mit der Data Interop-Erweiterung gehostet wird. Ich versuche, einen vereinfachten Workflow zum Laufen zu bringen (er verhält sich identisch zu einem Append-Tool), konnte jedoch keine Anhänge in einen Feature Service schreiben.<\/P> Zur Referenz: Ich verwende FME Workbench 2024.0.1.0 und ArcGIS Pro 3.1.1. Der Workspace ist wie folgt eingerichtet:<\/P> - Der Reader und Writer verweisen auf Feature Services, die auf ArcGIS Online gehostet werden. - "Ending_Locations_A_V2", der Reader, enthält 10 Features, von denen 2 Anhänge haben. - "Ending_Lovations_B_V2" hat genau dasselbe Datenschema und startet leer, Anhänge sind aktiviert.<\/P> <\/span><\/P>Ich konnte das Lesen der Anhänge bestätigen:<\/P><\/span><\/P>Dies läuft ohne Fehler und warnt nur darüber, dass OBJECTID und GLOBALID schreibgeschützt sind, was kein Problem sein sollte.<\/P>Jede Hilfe wird geschätzt!<\/P>-Brian<\/P> <\/P>

RenatoSalvaleon3 · Answer

@BrianGiroux I am glad we got this figured out with your AGOL to Enterprise attachment backup workflow.

Let me know if I can be of further assistance as you address the next step in your change detection workflow.

RenatoSalvaleon3 · Answer

My apologies for this delayed reply.  Data Interoperability does support writing attachments in AGOL (or Enterpise) primarily by using AGOL's REST API. This was my presentation at the last UC - UC24 proceeding to Intro to Data Interop technical session

Here's a guide on what to use in the ESRI stack when working with attachments.

Attachments in feature layers are blobs stored in the data store.

* HFL attachments have simple 1:M relationship in AGOL
* GDB or FS by reference use relationship class allowing 1:1 up to M:N.

Patterns of Use for reading/writing/moving attachments are the following:

For simple use cases, use core product tools (Python, GP tool)

* Attachments collected with ESRI Fields Apps

For complex workflows like below:

* Move attachments from non-ESRI to ESRI format
* Manage attachments, eg change detection 
* Store as hyperlink, database blob or file on disk
* Reports

Leverage the REST API and for tools use Data Interop of no-code/low code solution or Python or Notebook for coded solutions.

For the following workflows:

* Backup or Archive – use Replica or Download as FGDB (in the case of AGOL/Enterprise feature services with attachments)

Non traditional attachment questions can be addressed using Arcade as described in this Blog.

Please send me a note rsalvaleon@esri.com, if you want to pursue further a Data Interop solution. There is a clear pattern when working with attachments and each pattern would have some slightly different approach.

BrianGiroux · Answer

Hi Christopher,

Thanks for confirming my suspicion -- I'll have to look into the alternatives.

-Brian