Bug Report: search() Autocomplete Dropdown Fails on Repeat Instances Beyond the First (Survey123 Web App Only)
A select_one question using the search() appearance (autocomplete, filtered against a hosted feature layer via a value from outside the repeat) works correctly on the first repeat instance only. On the second and all subsequent repeat instances, clicking the dropdown produces no network request and no visible choice list at all — it is completely inert. This occurs consistently whether the repeat instances are generated via repeat_count or added manually via the "+" button.
This issue is isolated to the Survey123 Web App. The identical form (and the full production survey) works correctly in the Survey123 Field App on both Windows desktop and iPhone.
Environment
- Survey123 Connect version: 3.25.27
- Browser tested (Web App): Chrome 150.0.7871.130
- Field App tested (working correctly): Windows desktop Field App, iOS Field App (iPhone-OS 26.5.2)
- ArcGIS Online / Enterprise: AGOL org URL: clarion.maps.arcgis.com
- Survey123 Web App URL used for testing: https://arcg.is/j9qzn1
Steps to Reproduce (Minimal Reproduction)
A minimal XLSForm reproducing the issue is attached (FieldID_Dropdown_MinimalRepro.xlsx). It contains only:
- A top-level select_one question (ApplicationID) using search() against a hosted feature layer.
- An editable integer question (NumberOfFieldsInApplication, default 5) controlling repeat count.
- A repeat (FieldData) driven by repeat_count: ${NumberOfFieldsInApplication}, containing a single select_one question (FieldID) using search() with a matches filter referencing the outside-repeat ${ApplicationID} value.
To reproduce:
- Publish the attached form to [your AGOL org / Enterprise portal].
- Open the published survey in the Survey123 Web App (browser).
- Select a value for ApplicationID.
- In the repeat, select a value for FieldID on row 1 — this works correctly; a network request fires and the choice list loads.
- Advance to row 2 and click into the FieldID dropdown.
Expected result: The same search() query fires (filtered by the same ${ApplicationID} value) and the choice list loads, identical to row 1.
Actual result: Nothing happens. No network request is visible in the browser console (confirmed via DevTools → Network tab — row 1 shows a fetch request to the feature layer's /query endpoint; row 2+ shows nothing at all when the dropdown is clicked). The dropdown remains empty/unresponsive indefinitely.
Troubleshooting Already Performed (Ruling Out Form-Design Causes)
- Confirmed the issue persists using repeat_count and manual "+"-added repeat instances — rules out an issue specific to repeat_count generation timing.
- Removed all other calculationMode=always calculated fields from the repeat and surrounding form (pulldata-based lookups) — no change.
- Removed stray calculationMode=always parameter incorrectly present on the affected question — no change.
- Reproduced the issue in a minimal 2-question form (attached) with no other calculations, groups, or repeat content — confirms this is not an interaction with other form complexity.
- Confirmed the same search() mechanism works correctly for a non-repeated select_one at the top level of the form (ApplicationID), and works correctly for the repeated select_one (FieldID) specifically on the first repeat instance only.
- Confirmed the issue is Web-App-specific: the identical minimal form, and the full production survey, work correctly in the Survey123 Field App on both Windows and iOS.
Impact
This blocks our production workflow: a reviewer-facing survey needs staff to select from a filtered, dynamic list of records (via search()) once per repeat instance, and this is only usable via the Field App as a workaround. We would prefer our reviewers be able to use the Web App (desktop browser) for this review process.
Attachments
- Attached: Form1.xlsx — minimal reproduction XLSForm
YasserAyad_0-1785497266721.png
YasserAyad_1-1785497266724.png
Additional Notes
Related community reports describing similar symptoms (cascading/dependent select_one inside a repeat, filtered by a value from outside the repeat, working in Field App but not Web App) suggest this may be a known class of issue rather than isolated to our specific org/service:
- Esri Community: "Survey123 Select One Cascade Selects in Repeat not [working in Web App]"
- Esri Community: "Empty answer when editing a survey from Outbox or Sent folder, using relevant and choice_filter in nested repeats"
