Escribir Adjuntos en el Servicio de Entidades AGOL

Question

Me pregunto si alguien ha tenido éxito escribiendo adjuntos en un servicio de entidades existente alojado en ArcGIS Online usando la extensión Data Interop. He estado intentando poner en marcha un flujo de trabajo simplificado (actúa idéntico a una herramienta append) pero no he podido escribir adjuntos en un servicio de entidades.<\/P> Para referencia, estoy usando FME Workbench 2024.0.1.0 y ArcGIS Pro 3.1.1. El espacio de trabajo está configurado de la siguiente manera:<\/P> - El lector y escritor están referenciando servicios de entidades alojados en ArcGIS Online. - "Ending_Locations_A_V2", que es el Lector, tiene 10 entidades, 2 de las cuales tienen adjuntos. - "Ending_Lovations_B_V2" tiene el mismo esquema de datos exacto y comienza vacío, los adjuntos están habilitados.<\/P> <\/span><\/P>He podido confirmar la lectura de los adjuntos:<\/P><\/span><\/P>Esto se ejecuta sin errores y solo advierte que OBJECTID y GLOBALID son de solo lectura, lo cual no debería ser un problema.<\/P>¡Cualquier ayuda es apreciada!<\/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