Survey123 Connect update creating issues with web form

[ChandraLala]

Hi everyone, I was able to view my survey on the web perfectly fine before the recent update. After the update to Survey123 Connect (I am now using version 3.25.27), I receive an error message saying  "This survey cannot be opened in the web app. Please contact the survey owner to republish the survey with 'Create web form' enabled. Error: Missing .webform file." I can see in the survey files that a webform has definitely been created. I have tried republishing my survey and completely deleting it and publishing it as a new survey, and neither have fixed the problem.

I have experimented by removing certain parts of my XLSFormat table  to see if this fixes things. Removing certain questions and sections does fix the problem and allows for my survey to be viewed on the web, however this is not ideal because I need all sections and questions to be included. Please let me know if anyone else has experienced this and any possible workarounds.

EDIT: I previously thought this was an issue having to do with the update, though I was able to access an older version of Survey123 Connect and still experienced the same issues..

[ZacharySutherby]

Hello @ChandraLala, 

In Connect please select the Files button and open the file in your content folder called <yourSurveyName>.webform

If the contents of your webform file is a JSON error message that says "Error: Entity expansion limit exceeded: #### > 1000", this is a known issue with the 3.25 release and is logged as BUG-000183859​. 

If this is also what you see on your end please feel free to reach out to Esri Technical Support so you can be attached to the defect and track progress.  

[ChandraLala]

Thank you Zach, that is what I am seeing in my webform file. I don't have permissions to contact technical support... hopefully this can get resolved soon!

[TCKauhi]

As of today, I have this issue too and I am using Survey123 Connect v 3.24.31. It appears to be on one survey specifically, but I am concerned this is a larger issue. Is there a workaround, like going back to a previous version of Survey123 Connect? 

[ChandraLala]

I have a personal laptop with the same version as you installed. When I try to publish my survey using the older version, I get the same error as well. 

[ChandraLala]

The only temporary workaround I found is deleting some notes and questions from my survey.

On my personal laptop with the older version, I went into my XLSFormat table and deleted some frivolous rows (about 10). Once I deleted these rows, I was able to republish my survey and view it on the web correctly.

It seems like the issue has to do with the length of the survey. If the survey has too many items and questions, it doesn't display correctly on the web.

I haven't tested this on my work computer with the newest version yet, though I imagine the results would be the same.

[TCKauhi]

Hi @ZacharySutherby  and @ChandraLala, as you suggested, I did play around with my survey having issues and it appears that if I get the rows down to 100 or less (and republish) the survey does open in a web browser. However, removing rows to get it down to 100 or less rows is not feasible for this survey (so we still a workaround or permanent solution), but I thought that was good information to pass along. I have not tested this with other surveys yet or connect versions. Thanks!

[TCKauhi]

The hotfix appears to resolve our issue. I did have to republish my survey, and we are on Survey123 Connect v3.24.31. Thank you Esri for addressing an important issue quickly.

[TCKauhi]

Thank you @ChandraLala and that is interesting and good info. We are unable to remove any fields so we will have to wait for the bug to be fixed.

##EDIT## meant to say we cannot remove any rows (questions). We did try removing fields (columns) as indicated in the bug (removing language fields) but that did not work for us.

[MarlenaIsley3]

If you revert to the previous version of Survey123 v3.21.62 Connect, the web form issue goes away. However, now its not reading the pull data correctly.