We are launching a survey tomorrow using a Survey123 web form, published from Connect. In browsing through some test data colleagues have entered, I noticed that some answers for a particular question are being recorded as 'undefined'. This seems to only occur when the user is completing multiple repeats. In my own testing, I have now noticed that when I start entering data in to a second (or third, fourth etc....) repeat, the answer to the question (what Species did you see) in the previous entry becomes overwritten to a blank value. When checking the results, these fields are either left blank, or recorded as 'undefined' (screenshot attached), when they should contain the species name. In some instances, going back to a previous repeat to try and fill out the answer again after it has been removed by the subsequent repeat shows a greyed out box that cannot be filled in (screenshot attached). The only reason I can think this may be occurring with this particular field is because it uses a coalesce argument in the calculation column (workflow described below) or because the question is dependent on a choice filter / cascading select. This issue does not seem to occur if only a single repeat (i.e. the original repeat) is filled in. The form can be accessed publicly at https://survey123.arcgis.com/share/046b1389d4884f659e06baafba1119eb for reference.
Workflow leading up to the error:
Within a repeat
Breakdown of the erroneous behaviour:
In the results, this is stored as follows (with some dummy data) - errors shown in red:
Repeat number | species group (spgroup) | Species (SpeciesCo) | Scientific name (via pulldata function) |
---|---|---|---|
1 | Frog/toad | common frog (correct because this was filled in again after the last repeat removed it, but otherwise would be blank or show as undefined) | Rana temporaria |
2 | Newt/Salamander | blank (actual selection was smooth newt) | blank |
3 | Snake | blank (actual selection was grass snake) | blank |
4 | Lizard | undefined (actual selection was slow-worm) | Anguis fragilis |
#coalesce #repeat #Survey123 #webform #webapp #undefined
Hi Rob,
Did you ever find a solution for this? Please share if you did. I'm wondering if you have tested your survey in the field app? I understand you're using the web form but it may help uncover and equivalency bug if the issue only exists in the web form.
Thanks,
Brett
Hi Brett,
I ended up raising this as a support case (#02547150). The case resolution was it was a bug (BUG-000131208): 'Relevant calculation causes the selected cascade choice to disappear for the first repeat after filling in information within a second repeat (Survey123 web form)'. In the meantime I have had to put some workarounds in place until it is resolved.
Best wishes,
Rob