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

Comparer la valeur mise à jour à la valeur précédente ?

joyoung_kerrvilletx

Dans Microsoft Power Automate, quelqu'un sait-il comment comparer la valeur d'attribut originale à la valeur d'attribut actuelle lorsqu'une action "Fetch updates, changes, or deletions from feature layer" est utilisée avec un déclencheur "When a record is updated in a Feature Layer" ?

Il semble que le paramètre fieldsToCompare pour extractChanges soit ce dont j'ai besoin, mais je ne trouve pas comment définir ce paramètre dans Power Automate. Il semble également que supportsFieldsToCompare soit défini sur false pour tous mes services d'entités hébergés qui ont le suivi des modifications activé.

Je voudrais que les utilisateurs reçoivent des e-mails lorsque le statut d'un problème signalé a changé. Actuellement, j'envoie différents e-mails en fonction du statut actuel, mais les e-mails sont également déclenchés lorsque le personnel saisit des notes sur le problème signalé même si le statut n'a pas changé.

Trouver plus de publications taguées avec

Accepted answers

Akshay Harshe

@Joshua-Young We currently don't support `fieldsToCompare` in Fetch updates changes and deletions action but you can use layer queries which might not exactly solve the problem you have but you can only get the changes that matches the filter.

There is always an option to use Http Request built in action instead of fetch to send the parameters you need.

We do have this enhancement in our backlog.

All comments

joyoung_kerrvilletx

Editor tracking is enabled and there is no enterprise geodatabase involved with this hosted feature service. I have a support ticket open with Esri Support and they have been able to replicate that hosted feature services properly configured have the supportsFieldsToCompare set to false in at least ArcGIS Enterprise 11.4, 11.5, and 12.0. I recreated the data in an enterprise geodatabase and that got the supportsFieldsToCompare to be true, but now other extractChangesCapabilities are set to false and Extract Changes fails with an error "The field 'layers' is required" even though the URL has layers=0 set.

If support or I can figure out a way to get this to work, I will post it here.

Akshay Harshe

Is editor tracking disabled on your feature layer? Also, I not certain but it might be disabled if you have a FS referencing data from enterprise geodatabase.

joyoung_kerrvilletx

@AkshayHarshe thank you for the information. I tried using the "When a HTTP request is received" trigger only to find out that our instance of ArcGIS Enterprise 11.5 is hard coding all hosted feature services supportsFieldsToCompare property to false with no option to change it. So any extractChanges calls with the fieldsToCompare property fail.

abureaux

Assuming that the change is already made by the time the automation is triggered (would make sense).

In this case, I would use an intermediary database with limited information. E.g., ObjectID and Status. Use Power Automate to grab the recently edited item, then compare to the secondary database to see when the Status changes, and subsequently update the Status for that item.

While a little more work, this should work well.

Akshay Harshe

There is always an option to use Http Request built in action instead of fetch to send the parameters you need.

We do have this enhancement in our backlog.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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