File Question Not Loading in First Repeat When Embedded in experience Builder

[AnthonyJonesRSK]

Hi, I have quite a unique issue that has only started occurring today, which I believe may be related to a recent update. I have a web form embedded within Experience Builder with a repeat that has a file type question. This was working fine yesterday but today the file question in the first repeat doesn't work.  It appears in the form like the image below and when selected nothing happens. This happens whether it is a new form or editing an existing record. For existing records the file can be seen in the feature service but appears as below in the form. I've tested this in Chrome and Edge.

Bizarrely, this only seems to occur when the form is embedded. If I open the form outside of experience builder then the file question in the first repeat loads fine. 

I then checked the version of Connect being used and spotted the latest version is 3.22 and my form had been published in 3.21. I tried setting the form to use the latest version and found that for new entries the form would then work embedded. However, if I tried to edit a record the whole browser would crash and become unresponsive.

I have thought about upgrading S123 Connect to 3.22 but I'm wary of doing this given how unstable using the latest version in my 3.21 published form was.

Can anyone in the S123 team maybe look into any issues caused by the latest update for the file type question please?

Thanks

Anthony

[ZhifangWang]

Hi @AnthonyJonesRSK ,

The Survey123 website was updated yesterday, which may have caused this issue.

I was able to reproduce the problem in an Experience Builder app as you described. We are currently working on a potential fix and will keep you updated on the progress.

In the meantime, to work around this issue, please temporarily set the version lock for this survey to false. This will allow you to remain on version 3.21 until the fix is implemented.

[AnthonyJonesRSK]

Hi @ZhifangWang,

Thank you for coming back to me so quickly on this it's much appreciated. I've kept my form so it continues to use 3.21 for now as under 3.22 the browser just crashes.

I look forward to any updates on this.

Thanks

Anthony

[AnthonyJonesRSK]

Hi @ZhifangWang,

Unfortunately, I now can't access my form at all in my ExB app as I needed to make some unrelated changes this morning, republished my form but hadn't realised that Connect had auto-updated to 3.22. I now cannot revert to 3.21 and so my form crashes the browser every time.

Can this issue be escalated please as it's preventing our users utilising the app? Also, is there anyway for me to revert to 3.21?

Thanks

Anthony

[ZhifangWang]

Hi @AnthonyJonesRSK ,

Thank you for your patience. From the information you shared, we identified to issues after the Survey123 February 2025 update since last week:

1. A file question inside a repeat cannot load completely in the 3.21 web app.
2. For the edit mode (?mode=edit) in the 3.22 web app, if setting the default value for a note question type using the `?field=` URL parameter, the web app becomes unresponsive. This has been reported as BUG-000174625.

We have applied fixes to both issues on the Survey123 beta website, could you verify to see if the fixes work for you?

• To test the fix to the second issue, append the URL parameter `?survey123=env:beta` to the URL for your Experience Builder app. This URL parameter is used for development work and will load the Survey123 web app from the beta website. It will use the 3.22 web app on the beta website as your survey has been already published in the 3.22 Survey123 Connect
• To test the fix to the first issue, in addition to appending the URL parameter `?survey123=env:beta` to the Experience Builder app, you need to open the browser's developer tools and locate the Survey widget's iframe in the HTML, and then update its src (the URL of the embedded Survey123 web app) to append the URL parameter `version=3.21`. This will load the Survey widget using the 3.21 web app on the Survey123 beta website.

Please find attached the details for the above tests.

If you have a local copy of the installation file of the 3.21 Survey123 Connect, you can install it and republish the survey to revert it to the 3.21 version.

[AnthonyJonesRSK]

Hi @ZhifangWang,

Thank you for continuing to investigate this for me. So I've tried adding `?survey123=env:beta` to my experience builder URL and unfortunately this still causes the browser tab to become unresponsive as soon as I try and access an embedded survey that has the ?edit parameter. Surveys creating new records open without issue. Also I don't know if it's relevant but when launching my experience builder app in a new tab from the builder, both tabs become unresponsive if in either tab I try and access the form with the ?edit parameter.

I confess that I'm struggling a bit with the test to fix the first issue as I'm not quite sure how to find my embedded survey in the code. It's part of a section with a lot of views and only becomes visible when the user selects a button from a list. If I select the button the app will crash so is there any easy way to search the HTML to find it? I do have a call with a technician from Esri UK tomorrow so I can possibly ask them for assistance on this.

Unfortunately I don't have a local copy of the 3.21 installation file. Is there anywhere this can be downloaded from? At the moment the form crashing is the bigger issue so if I can revert back to 3.21 that would buy me some time as I can avoid the file question issue for now.

Thanks

Anthony

[ZhifangWang · Accepted solution]

Hi @AnthonyJonesRSK ,

We have updated the Survey123 website today with fixes to both issues I mentioned in the earlier post. Could you confirm if the survey works as expected now in your workflow?

[AnthonyJonesRSK]

Hi @ZhifangWang,

Thank you for working on this so quickly, it's very much appreciated.

I managed to find an installation file for 3.21 yesterday so republished my survey using that and I can confirm that the file question not showing has now been resolved. I'm reluctant to republish to 3.22 just now as I have a presentation on this app next week but I've just tested setting the survey to use the latest version and can confirm that the browser crashing issue also appears to be resolved so that is excellent and really appreciate the effort you and the team have put into sorting this.

Have a good day.

Thanks

Anthony