Latest Contributions by AkshayHarshe

I am creating this post to ensure everyone stays informed about the issue we discovered with the "When a survey response is submitted" trigger. Please note that this is still under investigation so there could be discrepancies or updates to the following information. This issue affects All connectors: ArcGIS, ArcGIS Enterprise, Survey 123 When we create a flow using the "When a survey response is submitted" trigger in Power Automate, it generates a webhook in the Survey123 App. Currently, the webhook is created with the default name MS-FLOW, whereas previously it was named MicrosoftPowerAutomate-[flowId]. When multiple flows are created for the same survey using this trigger in Power Automate, it fails to assigns unique names; instead, it replaces the existing webhook in the Survey123 app with the same MS-FLOW name. After conducting some tests, we have identified the following findings. We know the this behavior is due to a recent change by Microsoft, as they are transitioning their URLs from "logic.azure.com" to a new architecture using "api.powerapps.com" where the URL construction is different than before causing internal failures.  For reference, please see: Troubleshoot common issues with triggers - Power Automate | Microsoft Learn.  Unfortunately, we did not anticipate any issues with this change when we audited our code and it expressed itself in the Survey 123 app. We are working with Survey 123 team to investigate and resolve with best possible solution and as soon as possible. We apologize for any inconvenience. Please see following details and workaround.  Who is affected? Firstly, we think that Microsoft is still rolling this update and not everyone will experience this issue. If you are creating multiple Power Automate flows on a single survey with `When a survey response is submitted` trigger. If you have multiple existing Power Automate flows with this trigger and they not working or if you are trying to update or reauthenticate them. (Still investigating the impact please be mindful when updating your flows with this trigger) You are updating an existing flow with `When a survey response is submitted` trigger. You are turning on an older flow on a survey which has other associated flows with the trigger above. Who is not affected? You are creating a your first flow with `When a survey response is submitted` trigger using any the ArcGIS connector. If you are not creating multiple flows on the same survey using the trigger in Power Automate. Workaround If you wish to create multiple flows on a single survey using `When a survey response is submitted` trigger then  Create Flow 1 in Power automate and save it. This should create a webhook named MS-FLOW in the survey 123 app --> survey -->settings -->webhooks. Make sure to build the entire flow and save it before continuing to the next step. Rename the webhook under survey settings to something meaningful. If renaming produces an error try turning the flow off then on. This will delete and recreate the webhook in the Survey.   Repeat steps 1 & 2 to create additional flows Test if all the flows are triggering. Turning on older flows on a Survey that has other active flows Please be mindful when turning on an older flows on survey that has other active flows as it can replace an existing webhook on the survey if it is named "MS-FLOW"  Check your survey if it has a webhook called "MS-FLOW" Rename this webhook and test if it works. Turn on the older flow. This might create a webhook named "MS-FLOW" on the survey selected  Rename this webhook. Test all the associated flows on the survey work. Hope this helps. ... View more

We are pleased to announce a new set of updates in the 2025.3 release. For a quick read see What's new in ArcGIS Connectors for Power Automate Documentation. This release focuses on the enhancements in the "Get Data from Feature Layer" action as well as the Query functionality in our webhooks. Building upon the significant improvements introduced in the last release, these new features address key requests from our user community. Update: All Connectors are now live. Note: At the time of writing this article ArcGIS Online and PaaS connectors are rolled out by Microsoft and we are yet to receive these changes in ArcGIS Enterprise Connector NEW ACTION: Perform Geometry operations Available in all three connectors, this new action will include several operations coming from Geometry service starting with following two operations. See additional details on inputs and outputs here https://developers.arcgis.com/rest/services-reference/enterprise/geometry-service/  Areas and lengths This operation calculates areas and perimeter lengths for each polygon specified in the input array. The result is an output array of areas and lengths which should be in the same order as the input. At this time we only offer select units in our action. If this is not sufficient for your use please contact us. See Areas and Lengths for more details Buffer The buffer operation is performed on a geometry service resource. The result of this operation is buffered polygons at the specified distances for the input geometry array. NEW to ArcGIS PaaS Connector We are committed to improving the ArcGIS PaaS connector going forward, so you can let your users use ArcGIS Operations without having have their own ArcGIS Accounts. Through API keys you can let your clients access some of these actions. See how to create API Keys here. Enhance ArcGIS PaaS connector to support Get data from feature layer operation PaaS connector can now run Perform Geometry Operation action. New capabilities in "Get data from feature layer" action Update available in ArcGIS, ArcGIS Enterprise and ArcGIS PaaS connector. We are excited to see all of you use these capabilities in variety of ways. Building on the previous release we now added following functionality in this action. For more details on these operation please read up on Query (Feature Service/Layer) | ArcGIS REST APIs | Esri Developer Select Output Fields Users can now specify exactly which fields are returned in their query results. This improvement streamlines outputs, reduces unnecessary data, and enhances overall performance by reducing amount of data returned from the feature service.  Output Summary Statistics Users can now perform advanced operations by output summary statistics for any chosen fields within a feature layer. Furthermore, it is possible to select group-by-fields for these statistics, allowing for aggregation and the highlighting of key metrics. This enhancement simplifies the process of notifying stakeholders or updating dashboards with essential summary data, such as totals, averages, and counts, all without the need for external data processing. You will first need to select Yes to dropdown under Show statistics to run this operation. Choosing this will ignore some of the settings in other dropdowns. See the Query operation details mentioned in the URL above. Here is an example:  Order by fields You can now order the fields ascending or descending in your query output from this action.  Restrict triggers by Layer Queries When a record is created/updated in feature layer triggers in ArcGIS and ArcGIS Enterprise now offer enhanced control data that is returned. When configuring webhooks in fetching updates, changes, or deletions action, you can now apply a layer query by filling Fields to compare section. As a result, only features matching the specified criteria will be returned. ensuring that notifications and responses are both timely and relevant. You can use this in addition to Esri geometry filter. For more details see Extract Changes (Feature Service) parameters. Find address candidate (top candidate) is deprecated Find address candidate is deprecated from ArcGIS and ArcGIS Enterprise connectors but this will still be available in ArcGIS PaaS connector. Flow currently still using this action will continue to work. This action will not appear in the list of available actions. It is recommended to use Find address candidates action and the "Top candidate match address" instead. Other Enhancements Find address candidates action can now have single line address input. Administrators can now create webhooks on any feature services. Correct errors will be returned if webhook creation fails when the layer is not editable Documentation Actions and triggers documentation has been updated to include relevant links to the API for most of the actions. Added and cleaned up documentation. ... View more