Select to view content in your preferred language

Survey123 Widget Asking for Portal Login

104
1
Jump to solution
01-15-2025 07:18 AM
Labels (2)
emoreno
Regular Contributor

Hi ESRI community,

I am experiencing a problem with an experience builder we've had in production for a few months now. This experience has had no issues with it's initial configuration: a web map that displays data submitted through a Survey123 widget, as seen in the screenshot below. The survey is connected to our parcel data, which is also displayed in this web map, as we are auto-filling some address information.

emoreno_0-1736954195791.png

 

We started seeing an issue when we added a feature service from our Portal to this same web map, with the intention of having this layer be live from our internal database. This layer is shared to our AGOL VIA a distributed collaboration, and prompts users to sign in if they wanted to see its contents (as expected). The problem is that after the user either logs in to see the live layer or closes out the prompt, they are then asked in the Survey123 widget to sign into Portal again (twice). Is this due to the survey layer being in the same web map as the live portal feature service? Does anyone have a workaround that we would be able to implement? We would want this live layer to be available somewhere in the experience as it is used often by the stakeholders, but with as little login prompts as possible. 

Any advice would be appreciated! Thanks  

0 Kudos
1 Solution

Accepted Solutions
emoreno
Regular Contributor

The problem was the webmap within the survey itself was the same webmap being used in our experience. Since we had added a new portal feature service to the web map and required users to log in, the survey reflected this behavior as well, resulting in multiple login requests. 

We created a new webmap without the portal feature service for the survey, and it is working as expected. 

View solution in original post

0 Kudos
1 Reply
emoreno
Regular Contributor

The problem was the webmap within the survey itself was the same webmap being used in our experience. Since we had added a new portal feature service to the web map and required users to log in, the survey reflected this behavior as well, resulting in multiple login requests. 

We created a new webmap without the portal feature service for the survey, and it is working as expected. 

0 Kudos