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; } } }

"quando um registro é criado em uma camada de feature" também acionando em edições de feature

ahargreaves_FW

@SeanKMcGinnis Eu realizei alguns testes simples e posso ver o seguinte comportamento:<\/P>

Se eu configurar o flow conforme mostrado abaixo, ele funciona conforme o esperado e apenas<\/STRONG> envia um email quando novos<\/STRONG> registros são criados no feature service. <\/P>Quando um novo registro é criado<\/STRONG><\/LI>Aplicar a cada um<\/LI>Enviar email<\/LI><\/UL><\/UL><\/UL><\/span><\/P>O problema com isso é que não temos acesso aos atributos da nova feature/dynamic content.<\/P>No entanto, se configurarmos o flow conforme mostrado abaixo, agora ele fornece<\/STRONG> acesso aos atributos da nova feature/dynamic content, mas não funciona conforme o esperado. Em vez disso, ele envia emails para ambos<\/STRONG> novos registros e<\/STRONG> edições em registros existentes:<\/P>Quando um novo registro é criado<\/LI>Aplicar a cada umBuscar atualizações, alterações ou exclusões<\/LI>Aplicar a cada um 2<\/LI>Enviar um email<\/LI><\/UL><\/LI><\/UL><\/UL><\/span><\/P>Observe que há 2 payloads sob 'Aplicar a cada um 2'. Aqui está o JSON RAW:<\/P>ENTRADAS RAW DA AÇÃO FETCH:<\/STRONG><\/P>{<\/P> "host": {<\/P> "connectionReferenceName": "shared_arcgis",<\/P> "operationId": "WebhookGet"<\/P> },<\/P> "parameters": {<\/P> "changesUrl": "https%3a%2f%2fservices.arcgis.com%xxxxxxxxxxxxxxxxxx%2farcgis%2frest%2fservices%2fMSFLOWTESTING%2fFeatureServer%2fextractChanges%3fserverGens%3d%5b829542%2c829547%5d%26async%3dtrue%26returnUpdates%3dfalse%26returnDeletes%3dfalse%26returnAttachments%3dfalse",<\/P> "userLayer": "xxxxxxxxxxxxxxxxxxxxxxxxxlayerId0",<\/P> "layerId": 0<\/P> }<\/P>}<\/P> <\/P>SAÍDAS RAW DA AÇÃO FETCH:<\/STRONG><\/P>{<\/P> "statusCode": 200,<\/P> "headers": {<\/P> "Timing-Allow-Origin": "*",<\/P> "x-ms-apihub-cached-response": "false",<\/P> &n bsp; & nbsp ; & nbsp ; & nbsp ; & nbsp ; "x-ms-apihub-obo":& nbsp ; "false", & nbsp ; & nbsp ; & nbsp ; & nbsp ; "Date":& nbsp ; "Qua, 04 Jan 2023 19:35:22 GMT", & nbsp ; & nbsp ; & nbsp ; & nbsp ; "ETag":& nbsp ; "W/\"2d5-dilcTtnGDqgzN3ciuDdCj1NYU7E\"", & nbsp ; & nbsp ; & nbsp ; & nbsp ; "X-Powered-By":& nbsp ; "Express", & nbsp ; & nbsp ; & nbsp ; & nbsp ; "Content-Length":& nbsp ; "725", & nbsp ; & nbsp ; & nbsp ; & nbsp ; "Content-Type":& nbsp ; "application/json; charset=utf-8" & nbsp ; & nbsp ; & nbsp ; }, & nbsp ; & nbsp ; & nbsp ; "body":& nbsp ; { & nbsp ; & nbsp ; & nbsp ; & nbsp ; "items":& nbsp ; [ & nbsp ; & nbsp ; & nbsp ; & nb sp; & nb sp; { & nb sp; & nb sp; & nb sp; & nb sp; & nb sp; "geometry":& nb sp; { & nb sp; & nb sp; & nb sp; & nb sp; & nb sp; & nb sp; "x": -8597754.054998333, & nb sp; & nb sp; & nb sp; & nb sp; & nb sp; & nb sp; "y": 4702694.790991535 & nb sp; & nb sp; & nb sp; }, & nb sp; & nb sp; & nb sp; "attributes":& nb sp; { ... (continua com os dados JSON) ...

Observe que há 2 itens retornados pela ação fetch, mas nenhuma forma de discernir que apenas 'ponto 6' foi o registro recém-criado. 'ponto 5' já existia e foi apenas editado.

Portanto, @SeanKMcGinnis como configuro um flow para enviar um email somente quando uma nova feature for criada que também forneça acesso aos atributos/dynamic content?

(Para clareza Estou vinculando a postagens cruzadas relacionadas aqui)

Encontre mais publicações marcadas com

Accepted answers

AnthonyLatini

Hello @ahargreaves_FW ! My name is Anthony and am a product engineer on the ArcGIS for Power Automate team.

I wanted to give an update on this issue and fix. We have pushed a fix to ArcGIS for Power Automate and all tests have been completed. You should be able to run your flow again and see the correct behavior. In some cases, you might need to recreate your flow (Power Automate can be a tricky environment with caching, etc.).

As a note, I tested this using both email responses message in Teams. Further, I also tested this using some "extreme" flows where I was updating, deleting, and creating records all within a 30 second to 5 minute timeframe. I wanted to recreate the original flow as well as some extended testing.

Please let us know if you are seeing the original behavior that you posted or if there are any other issues that pop up!

All comments

Martin1

Hi @cmerwin,
Have you been successful in finding the reason why it did not work?

cmerwin

Hi Sean,

I do have an open case regarding this issue but figured I would try here also.

I've had flows running successfully for about 6 months now and they continue to work. However, any new flow I create simply does not. Everything connects, but when I go to test and trigger them, nothing happens. I've even gone as far as deleting all of my connections and reestablishing them and again, the existing ones run successfully but nothing new does. The very kind Technical Support person I've been working with and I are entirely stumped. Could the recent Microsoft outages have something to do with this? Any guidance would be greatly appreciated!

Attached is a screenshot of one of my very basic flows.

Kindly,

Cody

Screenshot 2024-08-02 085200.png

NAD.JPG

SeanKMcGinnis

I am glad it is working as expected and appreciate you working with us as we figured out the best solution. As always, you know where to find me if something comes up in the future.

ahargreaves_FW

@AnthonyLatini , @AlagiriVenkatachal & @SeanKMcGinnis initial testing of the fix shows it's working as expected and only NEW features are triggering the flow, not updates to existing features.

Thank you all very much for the rapid update.

AnthonyLatini

Hello @ahargreaves_FW ! My name is Anthony and am a product engineer on the ArcGIS for Power Automate team.

Please let us know if you are seeing the original behavior that you posted or if there are any other issues that pop up!

ahargreaves_FW

@AlagiriVenkatachal thanks for the update and thanks to you, @SeanKMcGinnis and the team for support and quick fix. Please can I ask you to post here once the fix is in place?

AlagiriVenkatachal

Hi @ahargreaves_FW ,

We found an issue with how we are processing the changesUrl from the payload for the webhook trigger. We have a fix for it and are in the process of testing it now.

Once we have tested the fix, we hope to have it deployed soon.

Best,

Alagiri

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

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