ArcGIS for Power Automate - v2022.1.5 - Change log and updates (August 11, 2022)
ArcGIS for Power Automate is updated regularly to provide new features, improved speed and usability, and bug fixes. The 2022.1.5 update is a quality release. Performance improvements and bug fixes have been made for the following features.
This release will start deploying between August 11th, 2022, and August 12th, 2022. It may take up to 48 hours to push out to all regions (up to two weeks for government-level sites).
If you do not see the changes, you may need to clear your cache and restart your web browser to see the changes in Power Automate.
As always, please let us know of any improvements or issues you want to chat about.
----
Geocoding (not stored)
A bug was identified in the ArcGIS for Power Automate connector when using an API key and geocoding locations in a flow. If the option "no" was chosen under "Store Results", the lookup process would fail and then the flow would ultimately fail.
This issue has been resolved and you can now choose any option and receive the appropriate results. This is an important fix because you might have your API key configured to not store results when geocoding.
Webhook creation when updating a connection
In Power Automate, you are required to keep your connections and credentials updated on a consistent basis. ArcGIS for Power Automate follows the same rules and connections to ArcGIS Online must be refreshed every so often.
In rare cases, if a flow contained a trigger to an ArcGIS feature service, the update of those credentials would create an additional webhook on the feature service itself. This ultimately caused an issue on the feature service as there is an upper-limit of 5 webhooks that can be created.
This issue has now been resolved. When a flow has its connection updated, the associated trigger and webhooks are updated and additional items are not created. This helps mitigate the new webhook creation on a feature service and does not max out the number of webhooks allowed.
Bug fixes and polishes galore!
In this release, we have squashed a ton of bugs and made some performance improvements to the connector.
----
As we continue to move toward the unified experience across all ArcGIS for Microsoft 365 visuals, we would love to hear your feedback, whether it be an idea or if something is broken. Having open communication about the visual and how we can improve will keep us moving forward and paving the way for GIS in the Microsoft 365 ecosystem.