How to create a Survey123 form for sequential evaluation of unique points in a hosted feature layer?

[MatejSvec]

Hi,
I’m trying to build a Survey123 form for a set of unique points stored in a hosted feature layer. Each point represents one location, and each location needs to be evaluated using three questions. The geometry of the points must remain fixed, and users should only provide the attribute responses. Ideally, the geometry (location) should be displayed for each point at the time of evaluation as a part of the form as a map.

My goal is to create an efficient, sequential questionnaire where the user evaluates each point one by one, without creating new records or modifying the point locations.

The problem:
I seem to be going in circles and cannot find a solution for hours. My main issue is that I cannot proceed the form for more than one point.

Question:
How can I configure Survey123 so that each existing point opens as its own form for editing, allowing users to evaluate all points efficiently and in sequence?

Thank you deeply as I’m starting to feel a bit frustrated. 🙂

[MobiusSnake]

Not really an answer to your question, but unless this needs to be done on a mobile device (or really, in a disconnected environment), I'd consider a dashboard instead.  I've used them for similar workflows in this way:

• Map to left of the dashboard, table of records to the right, with editing enabled on the table
• In the web map, configure forms to suit the review process you need in the dashboard
• Create a hosted feature layer view of the data and use it in the dashboard rather than the hosted feature layer itself.  Enable editing, but disable feature creation and disable editing on fields unless they're required to be edited by the review
• Add a new yes/no field for "Reviewed" and put it at the bottom of the form
• Either filter the view by the Reviewed field (so when the record is marked as reviewed, it'll disappear from the map and the table), or alternatively add a "Reviewed" column to the table and use it as symbology, so users can easily see what's been reviewed and what hasn't

[MatejSvec]

Thank you for the idea. It could be the solution.

The aim is to make the survey as easy as possible to encourage people to do it..
The goal of the survey is to collect as many responses from as many people as possible and calculate an average from them.
To simplify it, for example: You have 150 restaurants in a city and you ask people to rate each restaurant on a scale from 1 to 5.

[MobiusSnake]

Ah, that's a little different than what I was thinking about.

I have mobile users who collect data, but before it's used for analysis we have one user back in the office who reviews it (either the mobile user or a supervisor).  Once they've reviewed it, possibly adding notes to fields that aren't visible from Survey123, they mark it as reviewed - this ensures it's only getting reviewed once.

To capture multiple reviews for each record, it'll probably need to work a different way than what I had in mind.

[Neal_t_k]

One option could be to load the existing points/locations into the feature layer along with Site name and id and then use the inbox to load the survey allowing users to fill out the remaining questions.  You should be able to make the geopoint question read-only to keep the existing coordinates while allowing edits on appropriate questions.

The user would be able to fill out the forms in sequential order, however if it is required they fill it out in sequential order I am not sure how do that?   I also don't think you can turn "collect" off in the inbox, so users would still be able to create a new entry, but that could easily be handled on the backend...