Duplicates in select-one drop-down but not in XLSForm.

[SaraMiller]

Duplicate (triplicate/quadruple) instances of items in the Building select-one drop-down menu field, even though there is only one instance of each building in the Choice list.  To activate the Building list, a Location must first be selected.

Similar issue for the Priority select-one field, except it's a radio button style and it's showing two of each option.  The Priority field appears on pages 3, 4, 5, 6, and 7.  To get to it, select 'Yes' for 'Elements Recorded?', then expand the section for 'Grounds Elements Location' and 'Grounds Elements Details' section.  Then select 'Yes' for 'Inspected' and the Priority field will appear, showing the duplicate options.

Screenshots & XLS Form are attached.

[abureaux]

This is an old bug. From what I have seen, it seems to be largely fixed now. What version of Connect do you have?

[SaraMiller]

Thank you for getting back to me.  I thought it must be an older bug, but couldn't find any other threads about it (probably didn't use the right key words).  My Connect version is 3.14.256, but this survey has been running since 2021.  I've got the latest version of S123 field app.

[abureaux]

And if memory serves me, that was around the version that I saw this issue.

I would update Connect and republish (current version is 3.19.104). I would also recommend downloading the Windows Store version of Connect as it will auto update.

As a bonus, you can use the new Connect to update the old XLSX forms and check for any serious issues in said XLSX.

[SaraMiller]

Update:  I've now updated Connect to the latest version and republished the survey without making any changes, but it is still showing duplicates in my S123 field app.  What gives?

[abureaux · Accepted solution]

If you delete and re-download the form (in the Field App), the duplicates should stay away now. At least from my personal experience.

[SaraMiller]

Ahh, deleting and re-downloading the form instead of just updating it did the trick!  Thank you so much, @abureaux!