Survey123 removing already selected locations from list

[MikeAppel1]

I have a request from the field crew to limit a selection of locations seen on a specific question by several parameters (area and type of location). I used cascading selects to do this with no problem. But they would also like it to progressively remove locations they have already completed observations for during that field event. This is running inside a repeat so that only one survey is generated each field event. So after they completed the questions for location 1 in area a/type a, and they select a new repeat and select area a/type a, the list of locations that pops up will no longer have location 1 in there since it has already been completed. Is this possible?

[JamesTedrick]

Hi Mike,

Right now there isn't a way for a list to filter based on previous repeat values in Survey123.

[MikeAppel1]

Thanks. I figured not.

[JonMarks]

Hi @MikeAppel1 I realise this is a very old post but I came across it while looking for a similar solution so thought I'd reply in case it was of use. 

We have staff taking manual groundwater levels around a list of sites, I wanted to either have the select one list only contain the sites that hadn't yet been visited, but as this doesn't seem possible yet, I went about it a different way. I now have a text field that contains the remaining sites to be visited.

In the snip below I have a "join" field called Sites Visited that has all the sites from the repeat, separated by a line feed. The Sites Remaining field is generated using some JS that a machine wrote for me. As I complete each repeat, the Sites Visited field updates with the site name, and the site name is removed from the Sites Remaining field. You could always hide the Sites Visited field if you don't need both.

Some prerequisites:

My initial site list is from a CSV and I use a pulldata to populate the select one field.

I have a second CSV containing the same sites in a single field separated by semi-colons (generated from a script so that it is as up to date as the main site CSV file). This second file is of the format:

name,label
1,Coastal GW Zone at Faith P;Coastal GW Zone at Housiaux 2b;Hautere GW Zone at Jamieson etc...
2,Site1, Site2, Site3, Site4 etc...

Each site is separated by a semi colon rather than a comma, otherwise the pulldata doesn't work. The name column is  because I have two "runs" with different sites.

The text fields need to be larger than the default to handle all the site names, so make your bind::esri:fieldLength bigger.

Hope this is of use to someone. Critical files are attached.