Community

Survey123 - Performance Issues | Maximum number of questions

854
1
04-01-2019 12:27 PM
JordanMiller4
by
Occasional Contributor III
‎04-01-2019 12:27 PM

We've converting all of our forms from paper to electronic on an enterprise level but we're experiencing some performance issues with our survey regarding the number of questions and choices. We have 1 survey with 1 point and 27 nested related tables. The more fields and choices we add the slower it takes to open the survey and potentially crash. What's our best option moving forward? We still have a few forms we need to add.

IOS - 25 - 30 seconds to open | Version 3.3.40

Windows 10 - 1+ min  to open | Version 3.3.158

1 Point FC 

19 tables relating back to the Point FC

8 tables relating back to the various tables

926 Fields

Choices: 766

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍
# points
points = ["NEOForms"]

# tables
tables = ["ServiceRequest",
          "ServiceReport",
          "MaterialMovement",
          "MaterialMovementItems",#* Related to MaterialMovement
          "DIMP",
          "AbandonReplacementReport",
          "LeakSurveyLinePatrol",
          "LeakSurveyLinePatrolLocation",#* Related to LeakSurveyLinePatrol
          "PipelineInspection",
          "GasLeakandRepair",
          "LeakEvaluation",
          "OdorComplaint",
          "ServiceLineOrder",
          "OUPSCallinRequest",
          "MAOPCalculation",
          "MAOPCalcPipeUsed",#* Related to MAOPCalculation
          "MAOPCalcOtherAppurtenances",#* Related to MAOPCalculation
          "InlineValveDescription",
          "TestReport",
          "TestReportServicesTested",
          "PressureProblem",
          "RemedialActionReport",
          "RemedialActionCP",#* Related to RemedialActionCP
          "RemedialActionRectifier",#* Related to RemedialActionCP
          "RemedialActionKeyValve",#* Related to RemedialActionCP
          "RemedialActionOther",#* Related to RemedialActionCP
          "AtmosphericCorrosionReport"]‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍
0 Kudos
1 Reply
DougBrowning
by MVP Esteemed Contributor
MVP Esteemed Contributor
‎04-01-2019 02:05 PM

I would break them up into multiple forms.  Having one giant form with 900+ fields would be unbearable for the user and prob not a great design.

For us it was a plus since it allowed multiple workers on multiple tablets to work at the same time.  I did then create one master Feature Service that had all 9 forms tied together via relationship classes.  That way it is all in one place in AGOL but still broken up into digestible pieces.

0 Kudos