Survey123 Connect - Schema Preview Empty

[OscarSepulveda_III]

The Schema Preview within Survey123 Connect (v. 2.3.24) is empty for my form.  I have tried deleting the form folder and creating a new form utilizing the generic advanced template without success....

Anyone else have this problem?  

[KimHastings]

I'm having the same problem, and none of the suggestions in this thread have resolved it. I'm using Survey Connect 2.6.4. The form loads but the schema preview is empty. In addition, the cascading select is not working in the form. I have another form that uses the same cascading select and works fine, yet I can't see anything different between the two forms.

Maybe someone at Esri can take a look? I'm attaching the xls. [Edit: I deleted the attachment after the problem was solved]

[BrandonArmstrong]

Hi Kim,

I took a look at your XLSForm and see that you have several 'Calculate' fields that have a value of '0' in the calculation column.  I'm assuming that this was done in order to prevent the questions from appearing in the survey?  If so, I would recommend converting these question types to 'hidden' and removing the calculation value.

After testing with your form, I found that removing the calculation value from your 'select_one WorkUnits' question repaired the Schema Preview.  In addition, the question type was missing the '_' in 'select_one'.

Please try to make these changes and let us know your results.

Brandon

[KimHastings]

Thanks Brandon, your fixes solved all the problems with that form (even one that I didn't mention).

I inherited this survey from its original designer, so I don't know why he didn't use 'hidden' instead of 'calculate' for those other '0' fields, but your suggestion seems like a better approach.

[AdamDaily]

select_one question types don't play well with calculations. I am curious what the "0" value calculations in other calculate fields do though?

[KimHastings]

Adam, those other fields are placeholders, not used during the survey but needed later. The survey is actually gathering data that is ultimately destined for a SQL Server database and those are key fields for that DB. In post-processing (after the survey data are downloaded from the AGOL feature service, and before they are uploaded to the SQL Server DB), the SQL Server DB is queried and those fields filled in with the next unused key values.

This is just one part of a crazy Rube Goldberg-style setup that no sane person would touch, but I inherited it when the designer moved on, and I'm just trying to keep it running until we can redesign from scratch. 

[AdamDaily]

Thanks for clarifying and best of luck handling that system.