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

Datensatz in Enterprise Feature Layer kopieren, wenn zugeordnete Tabelle aktualisiert wird

AnninaRupe1

Ich arbeite seit ein paar Jahren an einem Tool und habe es langsam basierend auf Benutzerfeedback und Bedürfnissen aktualisiert. Dieses Tool verwendet Microsoft Power Automate, um viele Daten in verschiedene Layer zu kopieren, sodass Benutzer dies nicht manuell tun müssen. Der letzte Teil des Workflows nimmt ein Polygon und einige zugehörige Attribute aus einem ArcOnline gehosteten Feature Layer und fügt sie in einen Feature Layer in unserem Enterprise-System ein. Ich hatte Unterstützung von Esri, um dies zum Laufen zu bringen (wir hatten Stunden durch die Vereinbarung unserer Organisation für technische Hilfe). Ich habe einen Screenshot des Flows angehängt (Copy_to_Portal_PA.png).

Ich teste jetzt einen Prozess, um zu sehen, ob er als Lösung für ein Problem machbar ist, und es scheint, dass es funktionieren wird, aber ich habe die spezifischen Flow-Schritte nicht korrekt. Ich möchte erneut einen Polygon-Datensatz von einem gehosteten Feature Layer in den Layer unseres Enterprise-Systems kopieren, aber der gehostete Feature Layer hat jetzt eine zugeordnete Tabelle. Der Auslöser zum Kopieren des Datensatzes ist die Aktualisierung eines Attributs in der related Tabelle, wobei das übergeordnete Polygon, einige Attribute des Elternteils und einige Attribute des Kindes in den Enterprise-Layer kopiert werden. Ich habe diesen großartigen Beitrag verwendet, um die related Tabelle in Power Automate "sehen" zu können, aber mein Flow wird nicht ausgelöst. Basierend auf der vorherigen Unterstützung von Esri gibt es einen zusätzlichen Schritt / fehlenden Schritt / falsch verschachtelten Schritt, der dies verursacht, aber ich kann ihn nicht finden. Kann jemand helfen? Ich habe zwei weitere Screenshots meines neuen Flows (PA_1.png und PA_2.png) angehängt, um zu zeigen, was ich erstellt habe. Bitte lassen Sie mich wissen, wenn Sie weitere Informationen benötigen.

@NataliyaLys @SeanKMcGinnis

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

Akshay Harshe

@AnninaRupe1 Thanks for your question, I or someone else will look into this. Is the flow working and not doing what it supposed to? or Do you see an error somewhere

AnninaRupe1

@AkshayHarshe: I'm actually talking with a couple of solution engineers who will be reaching out to you more about my workflow! But for now, I don't have any errors to pass on because the Flow isn't being triggered, even though I updated the attribute that's supposed to trigger it. I basically copied the original Flow that runs fine and added the related table aspect, and now it doesn't trigger at all.

Pavel148

Hi, from the image, I do not see any issues with the flow, but I have some questions: 1- Why are you using 'terminate' at the end?
2- What are the response and initialization actions (actions 2 and 3)?

Just to confirm that your issue #1 is that the flow is not being triggered.
To assist here, please check if the flow was saved successfully.
Please check this screen to ensure no alerts are shown:

Check that the target layer is the layer you are editing. Not a view or vice versa.

Pavel148

Hi, in addition to other comments, please confirm if the record that is supposed to trigger the webhook has been edited or deleted by another system?

AnninaRupe1

I have created a brand-new hosted feature layer to test out my workflow; the record that's supposed to trigger the webhook is only being used for this new Flow and isn't being edited/deleted by anything else.

AnninaRupe1

I actually don't know the exact reason why the terminate, response, and initialization actions were needed. I have a Flow that's currently being used to copy from a hosted feature layer to an Enterprise layer (same workflow except without the related tables). I was having trouble with this last year and was able to use some technical assistance hours to get Esri help in creating the Flow. The analyst added these actions.

I opened the Flow and made sure the connections were good and saved it. At the top of the Flow, it stated that it was ready to go (see the attachment called Save_Successful.png). Then, when I returned to the Flow's management page, it gave me an error (see the Flow_Checker_Error.png attachment). I then clicked on the "Go to the trigger" link and the Run Details stated that there was an "Error creating webhook" (see attachment called "Error_Creating_Webhook.png). I did a bit of research and found that I didn't have the "Keep track of changes to the data" setting turned on. After I updated this setting in ArcOnline, the Flow triggered. However, the conditions were set incorrectly so the Flow didn't complete. I updated the conditions and the next time I updated the attribute to trigger the Flow, it failed (see the Flow_Fail.png screenshot). The "For Each" actions wouldn't stop spinning so I can't see what the error is there. I also don't know why there are so many "For Each" actions; they just keep getting added when I added other actions to my Flow.

The target layer is a hosted feature layer; not a view.

Error_Creating_Webhook.png

Flow_Checker_Error.png

Flow_Fail.png

Save_Successful.png

AnninaRupe1

I did some more testing:

I modified the Flow down to the bare minimum so I could first test the Trigger:

When a record is updated in a feature layer (related table)
Get data from feature layer (parent table)
Initialize variable
(Apply to each) Fetch updated, changes, or deletions from feature layer
(For each 2) Condition
- True
  - (For each 1) Send an email
- False

The Trigger works: I updated an attribute in the related table and it sent an email.
However, the data in the email aren't correct. In my hosted feature layer, I have two polygons. One has one related record and the other has two related records. I only updated one attribute in one related record of the related table of the polygon that has two related records. I received two emails, both with the same data from the updated related table record but the parent polygon data were for different polygons. So it sent an email for both polygons but assigned the same related record to both.
To me, this means that the related table isn't connected to the parent layer somewhere. I tried to put a condition in (ParentRecord (attribute from related table) is equal to GlobalID (attribute from parent layer)), but when the Flow is triggered, it follows the "False" part of the flow.

AnninaRupe1

Been working with a great team of Esri analysts! Here's an update:

Whittled the flow down to this:

When a record is updated in a feature layer (related table)
Fetch updates, changes, or deletions from feature layer (related table)
Condition (Specified one attribute change to listen for)
1. If true:
  1. Get data from feature layer 1 (parent geometry)
  2. Still having issues with this: Convert date and time format (target layer needs date only, not epoch or date/time)
  3. Create a record in a feature layer

If I remove the date attribute to write the Flow works. Looks like the big issue was flipping when to fetch related table updates and getting parent data. Will update more when I can!

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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