nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Power automate ArcGIS Connectors para capa de entidades AGOL (alojada, vista)

LouiseG

Hola Comunidad ESRI, estoy buscando documentación o consejos sobre cómo usar Power Automate ArcGIS Connectors para capas de entidades de ArcGIS Online (alojadas, vista). <\/P>

Tenemos una Capa de Entidades Alojada editable, y estamos usando Power Automate para: <\/P>

1) Publicar un mensaje en un chat grupal llamado MS Teams cuando se crea una nueva entidad<\/P>

2) Publicar un mensaje en un chat grupal llamado MS Teams cuando se actualiza una entidad<\/P>

Desde la Capa de Entidades Alojada, tenemos seis capas de entidades editables (alojadas, vista). Las ediciones se harán en estas capas de vista en lugar de la capa principal alojada. <\/P>

Hemos creado los flujos de trabajo de Power Automate, pero solo se activan cuando los ArcGIS Connectors apuntan a las capas de vista, en lugar de a la capa principal alojada. Leyendo otras publicaciones de la comunidad (por ejemplo, aquí<\/A> y aquí<\/A>) parece que los Power Automate Connectors necesitan apuntar a las capas de vista. <\/P>

¿Alguien podría aconsejarme si esto es correcto? Nos parece excesivo tener que habilitar 'Keep track of changes to the data' en cada capa de vista, y potencialmente crear 12 flujos de Power Automate. <\/P>

Muchas gracias, <\/P>

Louise<\/P>

<\/P>

Encuentra más publicaciones etiquetadas con

Accepted answers

abureaux

What is your trigger for the flow? Anything that isn't on a schedule (e.g., something that runs every x minutes) can result in delays. For example, any time I have a flow with "When an item is updated", it can either trigger instantly, or a minute later.

And to add on to that, email/email servers can also be slow. I've watch a multi-part approval flow finish to completion, and then 30 seconds later get several emails back-to-back for the different flow steps. Teams would be the same as this.

Personally, I hate the reactive triggers as they never seem to trigger when I expect them to. Also, I find the Survey123 reactive triggers (which I used a lot) very unreliable. Instead, I put everything on a schedule, and if nothing is found the flow is cancelled. I've never had a problem with this, and if an error is encountered, the flow can just reset and try again later.

I will add that if you go with the schedule approach, you need a dedicated field that can updated by the flow so once something is processed, it isn't reprocessed unintentionally.

All comments

abureaux

I don't think any of my flows are pointing to View layers, so that sounds wrong to me. Using the main FL should work, since that is where all the data ends up.

Akshay Harshe

Agreed to the comment above. It is requirement of webhooks to have changes tracking enabled and ArcGIS connectors have the same requirements for you to trigger the webhook. Webhooks in ArcGIS Online—ArcGIS Online Help | Documentation

LouiseG

Thank you @abureaux and @AkshayHarshe for getting back to me.I can confirm that changes tracking is enabled on the main hosted feature layer.

I turned off the Power Automate flows connecting to the view layers and did some testing today with the Power Automate flows connected to the main hosted feature layer. I created a point on a view layer but it didn't generate a MS Teams notification, then I waited a few minutes and tried it again but got no notification. Then a few minutes later I created a point on the main hosted layer, within two minutes I got two MS Team notifications at the same time for all three created points.

I have done some testing on the webhook using webhook.site. I do not receive a POST from the webhook when a feature is created on the View layer, but I do receive a POST when a new feature is created on the main feature layer. I have tested this with the webhooks created by Power Automate and with another webhook created in ArcGIS Online.

abureaux

I will add that if you go with the schedule approach, you need a dedicated field that can updated by the flow so once something is processed, it isn't reprocessed unintentionally.

Akshay Harshe

Triggers by nature are reactive, what @abureaux is a way you can bypass the triggers and check periodically to see if there are changes. It does add overhead but could be useful in certain scenarios.

How the webhooks are triggered is completely out of control of ArcGIS for Power Automate connectors. ArcGIS Online/Enterprise webhooks handle everything. Power automate is and our connectors will only know to run a flow when the Webhook says that it has new changes. The fetch action will get run extractChanges endpoint on Feature Server to retrieve changes that webhook collected. It is normal to have some delay running a webhook as someone making several edits to features layer(s) gets pooled to trigger once instead of making lot of requests.

LouiseG

Hi @abureaux and @AkshayHarshe

Thank you both for your advice on my query.

I was using the 'When a record is created in a feature layer' trigger, this works as expected when edits are made to the main hosted feature layer, but not when edits are made through one of the view layers. This seems to related to the webhook rather than the connector/trigger.

I have recreated the flow so it is now on a schedule and uses a control field as suggested here: https://community.esri.com/t5/arcgis-survey123-questions/generate-feature-report-in-power-automate-directly/td-p/1384495 (again, thank you @abureaux for this resource). The flow now posts a MS Teams message regardless of whether the edits were made on the hosted layer or the view layer.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.