Si has escuchado a personas mencionar webhooks, pero no estabas seguro de qué son - <\/SPAN>webhooks<\/A> permiten que los servicios web proporcionen a otros servicios información casi en tiempo real usando solicitudes HTTP POST.<\/SPAN><\/P>Los webhooks de capas de entidades<\/A> se activan por un evento, como crear, actualizar o eliminar registros en una capa de entidades alojada. El Conector ArcGIS para Power Automate<\/A> tiene disparadores que pueden crear y configurar webhooks para permitir que los flujos de Power Automate usen la carga útil de la respuesta y los datos para ser usados por otras acciones.<\/SPAN><\/P>
I'm running in to trouble with Table layer types. When using the Fetch updates, changes, or deletions from feature layer action, whenever I select a feature layer that is a table, I get the following error when trying to save.
Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'arcgis' operation 'GetFeatureLayerResponseSchemaForWebhook' failed with status code 'BadRequest'. This may indicate invalid input parameters. Error response: { "message": "Cannot read property 'toLowerCase' of undefined", "error": {} }'.
Is there a special process for table layers? Or are they simply not supported?
@SeanKMcGinnis
Thanks for all the information on this post, it's been very helpful to get set up with this new connector!
I am running into an issue with the Fetch Updates action. The flow is able to see that a change occurred in the hosted feature service, and if I have it set to send an email directly from that trigger, it works just fine. But when I add the step to Fetch Updates from the updated record, the flow fails. The output error is "Unable to synchronize replica", code 400. I checked in my hosted feature service that all editor tracking is enabled.
Any thoughts on what to change?
Thank you!
That is an interesting issue and since it is a 400 error coming back from the service, it leads me to believe it is something going on at the service level and not in the connector. I did some research and there are a few community posts (Post 1, Post 2) where others have encountered this and it is the result of the service’s source data.
My suggestion is to check the two community posts and if it continues to open a support ticket. If you do open a support ticket, could you please send me an email at smcginnis@esri.com so I can follow along in case others encounter the same issue?
Hi @SeanKMcGinnis ,
Thank you for being a resource in this esri community thread.
I am following your Power Automate workflow in attempt to post using the trigger: New record in a feature layer.
I have confirmed that following options are in the Editing settings are checked:
The flow is simply not triggered when adding a new record into the feature layer.
Is there any advice or work-arounds you can propose to troubleshoot in order to get this trigger to fire?
Thank you.
@JoeyCoscia - my first question in troubleshooting is how is the feature layer being edited (desktop client, web app, Field Maps, etc)? My next question is the application performing the edits going against the feature service itself or was an editable view created for the application to work with?For a technical way to test, I use Webhook.site and perform an edit, update, or delete to see if the webhook is firing to another client.
It does seem like the issue I raised above is due to a problem with the HFS. Creating a new version of the data/HFS has fixed the issue but ideally we can fix the issue with the old HFS. Working with ESRI on that.
In the meantime, I am working on creating my email flow with the ArcGIS Connector for Power Automate. When I've used the Survey123 connector, I've used the method from Ismael here to convert times in the emails. It does not seem to work quite the same with the ArcGIS connector. Any idea on how to convert ESRI time (in seconds) to a normal time and date?
@MeganHicks Can you expand on what is different or what you are seeing in the conversion? How is the date/time coming back to you?
I wrote up a post on how I Convert Epoch Time to a Human Readable Date Format, maybe give that a shot?
Thank you for your prompt response.
The feature layer being edited was through an AGOL web app.
The issue was with the 5 webhook limit that is imposed on a feature service. I had to go into the webhook manager and delete some other connections!
@JoeyCoscia - I am glad you found a solution to the problem. I am wondering, was it returning an error message? If it wasn't, it makes me think we need to make the creation process a little more robust and provide a more meaningful message.
Hi @SeanKMcGinnis
On August 2022, you talked about the possibility of at the end of 2022 Power automate could allow these arcgis Power automate new functions in ArcGIS Enterprise. Do you have some news about it?
Thanks a lot
Hi @BrunoGomesdeSouza - there are so many threads where people are asking for info about this, it looks like I missed one. The ArcGIS Enterprise Connector for Power Automate is currently in Microsoft's Preview environment. We are finalizing our testing on the connector and will be promoting it to General Availability in the next week or two.
It's amazing!
You gave me a good one news.
Thank you so much!
Finding this information has been a welcomed surprise! In playing with the flows, I'm able to add the record to my feature layer, but it's not updating on my map. I'm hoping to be able to have a SharePoint list trigger a Power Automate flow that will pull the an address from a SharePoint list and add it to my feature layer and display the new point on my map. In an ideal world, that new point would then be included in my buffer layer and would have my 1000' buffer around it. So far, I'm only able to get the new address added to the layer, but nothing ever shows up on my map. I do have the refresh set for both my feature layer and my analysis layer. What am I doing wrong?
Hi @SeanKMcGinnis , how are you?
Any news about Power automate new functions in ArcGIS Enterprise?Did you have released?Thank's
Hi Bruno, that's great. We work with ArcGIS Enterprise 10.9.1, does your procedure supports this version or is just for 11.0 and above? When I came to step 7, for testing the connection, after Test new connection the Test Operation button is disabled, is not clickable and I cannot figure out why. Have you got some idea? Thank you!!
@JonDolphin @BrunoGomesdeSouza - Hello! We are currently testing the ArcGIS Enterprise connector in our Preview region. Once we have finished testing, it will be available for general availability. This should be within the next 4-6 weeks as we need to work through Microsoft's submission process.
Some notes about the ArcGIS Enterprise connector in Power Automate. We are working on this connector in two different phases. In the first phase, we are supporting CRUD-based operations and a preview action of fetching updates and changes on feature layers. Later on this year, we will be adding support for geocoding, geoenrichment, routing, networking, and webhooks.
We will also be working with the ArcGIS Enterprise team to fully incorporate webhooks.
Once we have deployed the connector to general availability, we will provide instructions on how to use the preview version of webhooks in Enterprise 11.1 and above.
Environments supported: 11.0 and above / 11.1 is required for testing webhooks
Actions supported:
Note: This screenshot does not include the Fetch updates, changes or deletions from feature layer which will be a preview action.
Let me know if you have any questions!
Are there any ArcGIS specific Power Automate tutorials available for further information?
I've had no issues setting up a flow using the Survey123 When a survey response is submitted trigger. I was hoping to use the When a record is updated in a feature layer trigger to automatically send an email when a feature is updated and a specific condition is met but I don't see any options to select and filter specific attributes from my feature layer. For example, one of my conditions will include a status of "completed" i.e. I only want an email to be sent when a feature is updated and the status field is set to "completed". I've had no problem implementing this with a Survey123 trigger but in this case I'm looking for an update to a feature layer that is edited in the Field Maps App.
@SeanKMcGinnis Thanks for all the great info!
I'm trying to use the "When a record is updated in a feature layer" trigger to send an email when a feature is updated and a certain condition is met.
It worked initially, then, without changing anything in the flow or feature layer, it stopped working. The flow appears to run fine, however sometimes it registers the condition as false in cases where it is true, so an email is never sent.
Any tips? Thanks!
Hi Sean,
A while back in this thread you spoke about a single trigger for multiple feature layers/views. I currently have a project where we have a supervisor editing the base hosted feasture layer and then a contractor editing a hosted view created from that. When the contractor marks a task as complete, it generates a new one for the supervisor to do, but it is not triggering because it is coming from the view, however when the feature layer gets edited, the changes from the view are reflected through the webhook.
But to get the action to happen from just the contractor view edits, is the process still needing 2 webhooks for this situation? How does it avoid duplicating actions?
EDIT: I ended up creating a Solution in Power Automate where I have two Parent flows with the triggers of "When a feature is updated" for each the supervisor and contractor layers I have, however it's been creating duplicate data. The one I have tracked down had a flow run at 9:33am from the contractor view, and then 11:03am from the supervisor base feature layer. The editDate on the data in both flows is the same, so it had not been edited a second time since the first flow ran which was my first thought/concern. Any thoughts on the issue here? How does the "Fetch Updates" action know when it's been processed? Should I be adding a field to mark it as processed? If I change it to a flow that runs every 10 minutes instead would it avoid this issue?
Hi @RobertAnderson3,
Did you ever find a solution to this? I think I've stumbled across the same issue which I posted about here but have had no responses on it.
It would be very useful if "Fetch updates, changes, or deletions from feature layer" could be restricted to only pull changes related to the trigger. At present it seems to pull all changes which can be an issue when using views as it detects changes that may have already been processed when the view was edited separately.
@SeanKMcGinnis is this something that could be looked into please?
Thanks
Anthony
Hi @AnthonyJonesRSK unfortunately I don't think I really did. We ended up moving to python scripts in the hosted notebooks to run the process I was working on instead which avoided this.
I definitely agree that there needs to be a better strategy available in webhooks to avoid this type of thing when working with view layers though.
Thanks for the response @RobertAnderson3. My data was being edited in Survey123 so I ended up changing my trigger so it used the S123 trigger rather than "When a record is created in a feature layer". I'd originally used this in case my data was edited outside S123 too.
Anyway it would be really useful if "When a record is created in a feature layer" if that came with the data payload (in the way the S123 trigger does) rather than having to use "Fetch updates, changes, or deletions from feature layer" to get the information about the record created. The extra step is what was causing the issues for me as it was fetching data from the views too.
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
