Écrire des pièces jointes dans AGOL Feature Service

Question

Je me demande si quelqu'un a réussi à écrire des pièces jointes dans un service d'entités existant hébergé sur ArcGIS Online en utilisant l'extension Data Interop. J'essaie de mettre en place un flux de travail simplifié (il fonctionne de manière identique à un outil d'ajout) mais je n'ai pas réussi à écrire des pièces jointes dans un service d'entités.<\/P> Pour référence, j'utilise FME Workbench 2024.0.1.0 et ArcGIS Pro 3.1.1. Le workspace est configuré comme suit :<\/P> - Le reader et le writer font référence à des services d'entités hébergés sur ArcGIS Online. - "Ending_Locations_A_V2", qui est le Reader, contient 10 entités, dont 2 ont des pièces jointes. - "Ending_Lovations_B_V2" a exactement le même schéma de données et commence vide, les pièces jointes sont activées.<\/P> <\/span><\/P>J'ai pu confirmer la lecture des pièces jointes :<\/P><\/span><\/P>Cela s'exécute sans erreurs et avertit seulement que OBJECTID et GLOBALID sont en lecture seule, ce qui ne devrait pas poser de problème.<\/P>Toute aide est appréciée !<\/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