Nastavil jsem flow, které odesílá e-mail, když je vytvořen záznam ve feature layer v našem řešení citizen problem reporter. Používám konektor "When record is created in a feature layer" a poté akci "get data from feature layer" plus několik dalších akcí k získání nejnovějšího feature a zpracování JSON před odesláním e-mailu. Když kliknu na test v Power Automate a vytvořím záznam ve svém feature layer, flow se úspěšně spustí a odešle e-mail, ale když vytvořím nový problém v citizen problem reporter, nic se neděje, i když je nový feature úspěšně vytvořen. Flow je zapnutý a mělo by fungovat. Máte nějaké nápady, proč se to děje? Děkuji!

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

flow funguje při testování, ale v reálném světě nefunguje

MatthewAttiyeh1

Nastavil jsem flow, které odesílá e-mail, když je vytvořen záznam ve feature layer v našem řešení citizen problem reporter. Používám konektor "When record is created in a feature layer" a poté akci "get data from feature layer" plus několik dalších akcí k získání nejnovějšího feature a zpracování JSON před odesláním e-mailu.<\/P>

Když kliknu na test v Power Automate a vytvořím záznam ve svém feature layer, flow se úspěšně spustí a odešle e-mail, ale když vytvořím nový problém v citizen problem reporter, nic se neděje, i když je nový feature úspěšně vytvořen. Flow je zapnutý a mělo by fungovat. Máte nějaké nápady, proč se to děje? Děkuji!<\/P>

Najděte více příspěvků označených jako

Accepted answers

All comments

AnninaRupe1

@AnthonyLatini : any updates on this issue? I think I'm running into the same thing.

AnthonyLatini

@NataliyaLys - Thank you for the screenshot. That is the same behavior we are seeing with the multiple reports of this issue (empty brackets).

At the moment, there is not a workaround for this issue. However, we are investigating this issue and still attempting to get to the bottom of it. I will post to this thread and the others once we have a solution to this issue.

NataliyaLys

@AnthonyLatini thank you for the information.

I think that might be it, the issue with 'the first update'. I have a number of other flow, and they work fine, but they are not triggered by 'the first updated'.

Here is my output, and I'm getting just empty brakets.

Are there any workarounds for this issue?

Thank you,

AnthonyLatini

@NataliyaLys - Thank you for reaching out and sharing the flow information that you are having an issue with.

Currently, there is an outstanding issue related to retrieving updates from a feature layer that we are investigating and looking into. The bug does not appear to capture the first update that is made, but a subsequent update will be captured. In the first update, you may see an output that contains an empty result in the output section of the action: []

I am wondering if that is the reason for the flow not triggering or if there is in fact a parameter not being met.

Would you be able to share a screenshot of a flow that has run? I would like to check out the outputs of the flow itself. The output should look something like this:

Let's see if we can get this up and running for you!

NataliyaLys

I'm also trying to set up Power Automate to send an email notifictions when reports are submitted through ArcGIS Citizen Reporter application. And I'm running into an issue with one of my flows.

Here is my workflow:

1. Report is added through the citizen reporter

2. Status value 'Submitted' is assigned by default, when report is created

3. I have a python script running every 5 minutes, the scripts checks all new features added and based on location of the feature, it calculates' Geographic Assignment' field for each added report

4. Once 'geographic assigment' field is calculated I would like my Power Automate Flow to run, and make some aditional updates to the feature, and then send an email.

5. The flow is getting triggered, but it doesn't seem to pick up the edits so condition is not met and email is not getting sent.

I cannot figure out why the flow is not recognzing the update to the 'Geographic assignment' field?

A side note, the flow will run if I manually edit one of the fields (after 'geographic assignment' field was already populated)

Here is my Flow:

SeanKMcGinnis

I am glad we were able to help. I hope to have a blog posted on what we discussed to help others that might be running into a similar issue.

MatthewAttiyeh1

Just following up to let you know it seems like everything is working now! After connecting to the view layers and using the fetch updates tool everything seems be running smoothly. I appreciate all your help on this and thanks again!

MatthewAttiyeh1

I have been playing around with this and realized I didn't properly describe the problem in my first message.

I thought it was only working when using the test tool in power automate but now I realize it works when the flow is turned on but only when I pull the feature layer into ArcPro and create a new feature. When I create a feature using our public facing app nothing happens but when I create a feature within ArcPro I do get an email.

The webhook seems to be set up properly including the keep track of changes button and I have also tried the fetch updates action instead of the get data action but I am running into the same problem. The webhook just never seems to be triggering if I don't create the feature in ArcPro so it doesn't even get to the fetch updates action. This doesn't make sense to me because the webhook is connected directly to the feature layer so I don't understand why it makes a difference where the layer is edited from as long as a new feature is added.

SeanKMcGinnis

@MatthewAttiyeh1 - sounds good, please let me know how it goes.

MatthewAttiyeh1

Thanks again for the help on this. The first few parts were good to go but I haven't tried using the fetch updates tool. I will play around with it and let you know if it works for me.

SeanKMcGinnis

Good Day @MatthewAttiyeh1 ,

I was able to recreate the issue you were experiencing and I think I found a solution - it took a couple of steps, but I have gotten the web hooks to fire on submission of a request in the Citizen Problem Reporter Solution.

The feature layer that worked and fired the webhook was the 'Requests_reporter' which is a Feature Layer (hosted, view).

The red arrow is pointing to the feature layer view that is edited when a request is submitted through the Citizen Problem Reporter solution.

The next step was to confirm the 'Editing' settings are correct. For Power Automate to catch the web hooks, the 'Keep track of changes to the data (add, update, delete features)' must be selected. Initially it was not checked in the initial deploy of the Citizen Problem Reporter solution.

Make sure the 'Keep track of changes' check box is selected.

The next step was pointing to the Power Automate Trigger to the appropriate feature layer, which was 'Requests_reporter / undefined' and using the 'Fetch updates, changes, or deletions from feature layer' action to get the payload back from the web hook.

Screen Shot 2022-06-28 at 12.17.18 PM.png

Hopefully this helps, if it doesn't please let me know and we can continue to troubleshoot the issue.

MatthewAttiyeh1

Thank you for your response.

When I originally set up my flow I selected the layer form a dropdown in power automate from the ArcGIS connector. Just now I grabbed the feature Layer Id from the completed power automate record and when I looked that up in our system it shows up as a feature layer (not a view) but when I copy the url from that page into a browser it shows up as a featureServer with a different ID but shows the Service ItemID is the correct one (5fee9021128f4eb28efefc0b0e7ce024). I attached a couple screenshots to show you what I am talking about.

Let me know if that doesn't make sense but to me it looks like it should be connected directly to the feature layer right? Is there something I am missing? Should I actually be connecting to something else?

citizen problem.JPG citizen problem2.JPG

SeanKMcGinnis

Hi @MatthewAttiyeh1

I have run in to similar issues when setting up web hooks and accidentally pointing to one of the feature layer views and not the feature layer itself. Can you confirm which feature layer the web hook is being created against.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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