I'm looking to create a calculation that will search previous entries and populate the field with 'True' or 'False (or any similar feedback).
For example, if someone has previously submitted a survey with a SurveyID of '12345', when a new survey with the same SurveyID (i.e. 12345) in entered then the calculate field will identify that it already exists in the dataset and provide feedback accordingly.
I was looking at regular expressions that could suit my needs and it seems like match or search could do the trick but I can't figure out how to structure the formula so it works (although these functions might not be supported).
Solved! Go to Solution.
Hi David - It is not currently possible to have Survey123 query a feature service (containing the existing surveys). So you can't do a check on what surveyIDs have been previously used. I will however get this added as an enhancement request.
Would it be possible to use another approach and just ensure that you use a surveyID that is always unique - e.g. creating a string based on username and date?
Hi David - It is not currently possible to have Survey123 query a feature service (containing the existing surveys). So you can't do a check on what surveyIDs have been previously used. I will however get this added as an enhancement request.
Would it be possible to use another approach and just ensure that you use a surveyID that is always unique - e.g. creating a string based on username and date?
The purpose of the search would be to prevent duplicates reports for specific IDs that the user inputs. So the user is notified when the submissions already exists and then can search for that submission instead, or submit the new survey for a record that doesn't exist in the system yet.
I'll come up with a different approach until that functionality exists. Thanks for the response, Jonathan
Hi David,
Just letting you know that in the latest 3.12 beta builds available on the Survey123 Early Adopter Community we have made significant improvements to large choice lists which improve the survey load time in both Connect and the field app.
On top of this there are now some new ways you can manage your choice lists dynamically and update them without having to republish the survey, meaning choice lists can now be populated and updated dynamically from a CSV file or hosted table shared in ArcGIS or directly from a feature service using the search() function. Please check out the latest announcement on EAC and test out these new beta features with the latest 3.12 beta builds.
Regards,
Phil.