Introduction
We are excited to announce that you can now use Survey123 triggers and actions in both ArcGIS connector and ArcGIS Enterprise connector in Power Automate. In this blog, we'll guide you through essential information to ensure a smooth transition with minimal disruption to your workflows.
As we move forward, our primary focus will be on Survey123 triggers and actions in the ArcGIS connector and the ArcGIS Enterprise connector. This means we will stop adding new features to existing Survey123 connector. It is important to note that ArcGIS connectors for Power Automate are premium connectors and require a Microsoft 365 subscription or a pay-as-you-go plan to create and maintain flows.
Q&A:
Are the functionality of the existing Survey123 connector and the new Survey123 triggers and actions in ArcGIS connectors the same?
Yes, the functionality remains the same for now. However, new features will only be added to the ArcGIS connectors in the future.
Do I need to reconfigure my existing workflow?
Not immediately. However, you may need to switch to or use ArcGIS connectors in the future for new features of Survey123 triggers and actions.
How to migrate my existing workflows from Survey123 connector to ArcGIS connector?
The trigger and actions in ArcGIS connectors remain the same in terms of appearance and functionality, so there will be no user experience difference. Migration can be finished either by creating and switching to a new workflow or editing the existing ones.
How to migrate my existing workflow from Survey123 connector pointing to ArcGIS Enterprise to ArcGIS Enterprise connector?
The work for this question is pretty much the same as above question. As a matter of fact, creating connections when using ArcGIS Enterprise has been simplified. Instead of following this blog when using Survey123 connector, see this new instruction for making connections to ArcGIS Enterprise connector.
How can I avoid token expiration in ArcGIS connectors?
Check out this blog for valuable tips on keeping your connections valid and avoiding token expiration.
