Select to view content in your preferred language

Speeding Up Survey123 Form Creation for Large Surveys

105
2
Jump to solution
Monday
JoshuaFrerichs1
Emerging Contributor

I'm developing a digital version for the 2010 ADA Checklist for Existing Facilities document. There's about 93 pages worth of questions with each question containing, 1+ yes/no questions, measurement boxes, example pictures, place for comments and photos, and suggested solutions.

I started off building it with the online creator similar to the original form, using two columns to condense and hide/unhide conditional formatting to make it easier. However, now I'm over 1000 question blocks (question, comment, notes, images, etc.) and over 1GB+ in browser memory utilized with it open. Needless to say, its getting slow to continue.

I'm switching to Connect since it seems it could handle the length better, but I've gotten used to the ease of drag and drop elements. Is there any better way or easier way to set questions and formatting up in Connect? It would ultimately be a huge time save for us, I'm just struggling to finish the survey due to the shear size of it bogging down the online version.

0 Kudos
1 Solution

Accepted Solutions
ZenMasterZeke
Frequent Contributor

That's a bigger survey than maybe S123 is intended for. I can't imagine anyone filling out a 1000 question survey. The size will bog down AGOL whether you're using Connect or the web designer. If it's hosted on your own Enterprise server, that would depend on the server capabilities. A few suggestions, maybe you're already doing them:

  • If possible, break it into multiple surveys by topic, theme, area, etc.
  • Use groups and keep them closed by default
  • Keep questions hidden until/unless needed
  • Calculate any questions that can be
  • Provide defaults where appropriate
  • Add comments and suggestions later, after the survey is submitted, when reviewed

View solution in original post

2 Replies
ZenMasterZeke
Frequent Contributor

That's a bigger survey than maybe S123 is intended for. I can't imagine anyone filling out a 1000 question survey. The size will bog down AGOL whether you're using Connect or the web designer. If it's hosted on your own Enterprise server, that would depend on the server capabilities. A few suggestions, maybe you're already doing them:

  • If possible, break it into multiple surveys by topic, theme, area, etc.
  • Use groups and keep them closed by default
  • Keep questions hidden until/unless needed
  • Calculate any questions that can be
  • Provide defaults where appropriate
  • Add comments and suggestions later, after the survey is submitted, when reviewed
JoshuaFrerichs1
Emerging Contributor

Thanks for your response!

It's a pretty sizable survey, but they were originally using pen and paper and then scanning the surveys in. Not every question/section is applicable, but is included in the event that it's needed. One approach I'm implementing is allowing the user to select with Priority section they might need for that building. So instead of offering the full 4 priorities, they can cut it down to the ones they need in the moment. I'll try and cut out unnecessary questions/blocks to streamline it where I can.

0 Kudos