Latest Contributions by ISP_graynic

@ahargreaves_FW @m3  @AnthonyLatini I believe the error is because we do not have a public facing Portal. Our Portal is behind our firewall so it is unable to communicate with Power Automate. I just found on the ESRI website that is says "The organization must also be public-facing and able to receive requests over the internet."  Unfortunately there doesn't appear to be a workaround for this at this point.  ... View more

@LuisanaIG did you ever find a resolution to this? We are also getting this same error trying to connect in Power Automate. ... View more

Thanks for the response @AnthonyLatini! I verified that those redirect URL's were added. Our Portal is HTTPS, but I'm not sure about any rules with HTTP. We are running 11.2. It connects to our Portal to log-in and even seems to accept the user credentials, but then errors out as it's loading. ... View more

Has anyone experienced this error when trying to log-in to your Portal with the Connector? I was redirected to our Portal log-in and was able to log-in, but then I got this screen and was unable to actually create the Connector in Power Automate. @AnthonyLatini @ZachBodenner    ... View more

@AllisonLehn1 @patrickb  Any updates on the "contains" category selector option on Enterprise yet? I tried doing this in Experience Builder it just seems to clunky.  Has anyone else figured out any workarounds for filtering select_multiple fields from Survey123 in a dashboard on Enterprise?  ... View more

Hi @DavidNyenhuis1,   Are there any updates on actions for the List element in the mobile views for dashboards? Are actions supported in any of the mobile widgets? Thanks! ... View more

Has there been any updates to this? We really need the token to last longer than 14 days.  ... View more

It looks like only Actions are supported with the ArcGIS Enterprise Connector at this point. "Triggers, geocoding, GeoEnrichment services, network analysis services, and certain data retrieval actions are not currently available for the ArcGIS Enterprise connector." https://www.esri.com/arcgis-blog/products/microsoft-365/announcements/arcgis-enterprise-connector-for-power-automate/ ... View more

Anybody having any luck finding it in the gov cloud environment yet? @ahargreaves_FW @cblevins @ZachBodenner @AnthonyLatini  ... View more

I think I may have figured a workaround. In Step 7 "Add 3 Set Variable steps" I changed the featureLayerUrl to the the service URL of a view layer that's not shared publicly out instead of the dynamic value from the Parse JSON. It seems like adding a new entry to the public layer via the survey still triggers the flow but the actual report is generated off a view layer.  ... View more

I think the problem there is technically anyone who anonymously fill the survey out is out is seen as 1 user, so therefore it's their "own" features. Meaning anyone who submits anonymously can see anyone else who's anonymously submitted data which is what we are trying to avoid. That's why we had to change it to the last setting. I also have an email to an ESRI contact to see if they have any ideas.  ... View more

We are experiencing this same issue as random ones not triggering. ... View more

The account has admin privileges and since the survey is on AGOL I didn't create a custom connector but rather used the standard "When a survey response is submitted" in PA since the survey isn't on my own portal but just AGOL. The error message I get in PA is just a 400 error "This operation is not supported' when trying to create the report. When I change the feature layer settings in AGOL to the "Editors can see all features" however it works fine and generates the report.  ... View more

@abureaux Is there a way to have a feature report run on a layer that is not shared publicly in ArcGIS Online? I've got this to work in PA, but only when the layer is shared publicly with the settings below which exposes all responses to the general public. Basically I have a public facing survey where the "Editors can't see any features, even those they add" is selected so that the responses can't be viewed publicly, but when I have that setting PA errors out. It only works when I change that setting to "Editors can see all features" which exposes my responses to the public.  Thank you again for this post! It's a great tool.   ... View more

That should do the trick. Thank you very much! ... View more