building survey in AGOL using feature service from enterprise

[dsinha]

Hello,

I have created a survey using Survey123 Connect on AGOL. The survey uses a feature service on AGOL that is linked to a public hosted feature service in Enterprise portal. Data for this feature service is being collected using Field Maps. The purpose of creating a Survey123 form in AGOL using the Enterprise data is to use the report and export to excel functions in Survey123 (but missing in Field Maps).

The problem is that I cannot open Survey123 form using the Manage in Survey123 website option. The webpage keeps reloading constantly with the following error message: The survey is not accessible or does not exist. Please ensure the sign in user can access this survey and that the survey link is correct. Esri Tech Support pointed me to BUG #000167494 (The 'My surveys' page on the ArcGIS Survey123 website keeps reloading if a survey is published using a non-secure reference service added to ArcGIS Online.) but I do not understand how my reference service can be considered non-secure. Aren't the services secure by default? 

Any ideas? Thanks!

[jcarlson]

Any reason you can't just publish the form itself to your Portal? Why go through the AGOL connection?

[dsinha]

Because I cannot print reports in Portal.

[jcarlson]

The documentation may have misled you. You can't print reports through a self-hosted instance of Survey123, but there's no reason you can't use the AGOL Survey123 with portal-based feature layers and forms. Self-hosting Survey132 is extremely rare, you'd only do it if your organization had serious security settings in place.

When you go to survey123, just append the portalURL parameter, i.e.,

https://survey123.arcgis.com/?portalUrl=https://maps.co.kendall.il.us 

You'll see the connected portal in the upper-right:

You can absolutely generate reports this way. We generate dozens of reports every day through our portal.

[dsinha]

I tried it that way. But I received an error (agetaddrinfo ENOTFOUND) when trying to generate report for which I asked for help in this post on another forum (perhaps I should have posted it here). I believe its because our portal is not public-facing, but I could be wrong.

[jcarlson]

You can use this feature with private surveys and portals. When you attempt to use Survey123 with the portalURL parameter, it will communicate with your portal to properly authenticate you first. What is your portal URL? I won't be able to see it, but if I try to use your URL, it should prompt me for a login.

[dsinha]

Its: EDITED

[jcarlson]

Hm. I get a Server Not Found error. There's a difference between "not public facing" and "disconnected" I'd guess your site's security settings are configured to prevent traffic from outside of the network. In which case, yeah, you're kind of stuck not getting reports.

If the environment is disconnected, how does the AGOL collaboration work at all? Are you manually updating the AGOL layer? If your AGOL layer is just storing a reference to the portal layer, I would assume that it would not work.

[dsinha]

Yes, I am storing a reference to the portal layer in AGOL. And it does not work.

Thanks for clarifying that there is a difference between "not public facing" and "disconnected". We are running into problems with this with our Enterprise Field Maps applications too because our portal disconnects the moment we step out of our office network. Unfortunately, I haven't found any Esri documentation that explains how to "connect" to our data sources while remaining private facing. 

[jcarlson]

Okay, so that's a totally separate problem, and one that your org's networking folks will need to sort out. If you set your portal's settings to prevent anonymous access, nothing in the portal or server will be exposed to a user who is not logged in. You can further prevent users from browsing the REST directory of the server, too. These measures can be taken without restricting access to traffic entirely.

Alternatively, you could set your organization's security to allow IP addresses or domains used by ArcGIS Online and Survey123. No guarantee that those are static, so it could be a chore keeping those updated, but if you wanted to really clamp down on access, it might work.