Gravar Anexos no Serviço de Feição AGOL

Question

Estou me perguntando se alguém já teve sucesso em gravar anexos em um serviço de feição existente hospedado no ArcGIS Online usando a extensão Data Interop. Tenho tentado colocar um fluxo de trabalho simplificado em funcionamento (ele age idêntico a uma ferramenta de anexação) mas não consegui gravar anexos em um serviço de feição.<\/P> Para referência, estou usando o FME Workbench 2024.0.1.0 e o ArcGIS Pro 3.1.1. O workspace está configurado da seguinte forma:<\/P> - O leitor e o escritor estão referenciando serviços de feição hospedados no ArcGIS Online. - "Ending_Locations_A_V2", que é o Leitor, tem 10 feições, 2 das quais possuem anexos. - "Ending_Lovations_B_V2" tem exatamente o mesmo esquema de dados e começa vazio, anexos estão habilitados.<\/P> <\/span><\/P>Consegui confirmar a leitura dos anexos:<\/P><\/span><\/P>Isso roda sem erros e apenas avisa que OBJECTID e GLOBALID são somente leitura, o que não deveria ser um problema.<\/P>Qualquer ajuda é 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