Latest Contributions by SeanKMcGinnis

@RobertAnderson3  - there will be no impact to the flows currently using the Survey123 connector. But in order to take advantage of the refresh token management, it will require flows to be updated to use triggers/actions in the ArcGIS for Microsoft 365 connector. ... View more

@ChelseaRozek You are welcome for the update. I am not aware of any planned updates to Make. ... View more

Hi @ColForbin - the ArcGIS for Microsoft 365 team has been working with the Survey123 team  to address the issue with the refresh token not being renewed. We are going to bring the Survey 123 trigger and actions into the ArcGIS Connectors for Power Automate. This will address the two week timeout by leveraging the ArcGIS Connectors connection. We are expecting to have that migrated over with the next release which is slated for early summer of this year. ... View more

@COSPNWGuy & @ZachBodenner - the version of the Enterprise connector you are seeing was submitted to Microsoft in October. The version that has the triggers was submitted to Microsoft the end of January and  is currently being validated. Based on estimates Microsoft has shared previously, it is usually 8-12 weeks after initial certification, so rough timeline would be April~ish. ... View more

Hi @Judywatsonn - this does seem very peculiar. Have you submit a support request on this experience? Could you please email me directly at smcginnis@esri.com with the ticket number so we can help look into the source of the issue?   ... View more

Hi @erica_poisson, Unfortunately, the Survey123 connector is still using the older pattern of authentication. Our team is working with the Survey123 team to update the authentication pattern to the one currently in use by the ArcGIS Connectors for Power Automate. I do not have an estimate time when this will be completed, but when deployed (and promoted to GCC), it will address the timeout issue. As updating the connection so you no longer have duplicates, I go to the Survey123 Connection and click the 'Switch Account' button and re-enter my credentials. This renews the authentication tokens and prevents creating another connection. Switch Account process will allow you to reauthenticate the connection and keep all Flows running.   ... View more

Good Day @dolson_farmington - The previous version was not being promoted to GCC because there was an action tagged as 'Preview'. An updated connector was submitted to Microsoft and is going through their certification process. With this submission, all 'Preview' tags have been removed. There isn't a defined date when the connector will be promoted to GCC, but Microsoft's promotion timeline estimates that it will be in that environment in 6-8 weeks. ... View more

@TL2 - that is the Survey123 connector which uses a different authentication pattern than the ArcGIS Connectors for Power Automate and timeout every two weeks. The ArcGIS for Microsoft 365 team is working with the Survey123 team to update their authentication pattern to more closely follow our pattern. ... View more

@erica_poisson & @TL2 - thank you for the comments and sharing the way you are working with the token situation. There are two tokens that we are managing within the ArcGIS Connectors for Power Automate. The first is the session token which is what authenticates the user in the flow and is updated each time the flow runs. The second token is the refresh token, which manages the connection settings validating whether the user can make a request back to Online or Enterprise to get a session token. The expiration of this token is managed buy your Organization and by default is set to 14 days, but is configurable. Each time a flow runs we update refresh token, which in turn starts the clock to timing out against your Organization or Enterprise. If the flow has not run within the duration of your refresh token timeout, it will fail. The way I have been getting around this is I have a scheduled flow for each of my connections that runs on a daily basis to query against a specific feature layer. This forces the refresh token to be refreshed before it times out, preventing me from getting unexpected connection issues. I hope this helps and am open to any feedback or questions. ... View more

Good Day @Clayton-Cooley  - currently there are no triggers for ArcGIS Enterprise, but here is a blog post on you can enable webhooks and begin using the Connector. We are looking to deploy triggers in the Enterprise connector in conjunction with the ArcGIS Enterprise 11.2 release. ... View more

Hi @acarmody - the ability to create a flow by manually creating webhook following a similar pattern with ArcGIS Online is possible, but is not a direct product capability. The flow creation is less of a configurable component and more of a technical experience which goes against the intent for a no code/low code process builder.  The reason we are handling webhooks in the post you reference is due to differences in the way ArcGIS Online & ArcGIS Enterprise have implemented webhooks. The intent is to create a more consistent experience, modeled after the ArcGIS Connector, with the 11.2 release of ArcGIS Enterprise. It makes sense that the flow would become unresponsive if you changed the 'change type' to a wildcard would fail. The action has no concept of how to handle an asterisk. Could you please provide a little detail on what you are trying to accomplish by listening for all webhook types? Maybe submit it as an idea for consideration in future releases. ... View more

Hello @CScholer - thank you for submitting the idea and I am sorry you are encountering this issue. The token timeout issue for the ArcGIS for Power Automate Connector was resolved earlier this year, so I am surprised the you are encountering the issue. Are you working in a secured Azure Government tenant? If so, which one? A couple points regarding the other connectors you referenced: There is a known limitation with the Survey123 connector where their refresh token is still timing out in two week intervals. The team have upgrade plans to address this issue in the coming year. The ArcGIS Platform connector does not have capabilities to access hosted feature services. Currently it only accesses the location services that are delivered by platform. If you are having the timeout issues, I would suggest you submit a support ticket. ... View more

I think this is a really great idea. We are starting to plan for upcoming workstreams and will add this to the list of capabilities for us to consider. Thanks again and keep them coming! ... View more

@PatriceLabbé - as this is a new submission to Microsoft, they control the preview tag. We have submitted the appropriate details and asked them to remove the tag as it has passed all tests and has been promoted out of the Preview region. We support the product as we would any other ArcGIS component and are working with Microsoft to get the tag removed. ... View more