Reference error in Survey123 connect, and hangs when publishing

Question

Hello,

I created a survey in connect, and it was working fine until yesterday. Yesterday, I added a simple note field and not only it hangs publishing the update, now I'm getting all kinds of errors even when I delete the field.

While trying to test it in connect this is the error I get:

Also, the published survey fails submissions:

What has gone wrong?

SMH-Rio · Answer

Thanks for the reply.

The instance_name defines how the record appears in the field app when a record is edited (editing from Drafts, Outbox, Inbox). It accepts HTML formatting, functions, etc. Here is an example:

I hid personal information from users

As far as I know, the instance_name does not apply to the Web App, because there is no 'record list' for editing (the form opens directly, with all the data). It seems strange that this has a correlation with the problem. In any case, I will do some tests.

Rama1356 · Answer

The extended publishing time also happened when I added a new filed but in survey123 Connect. Hopefully they are working on it.

But if you're not able to submit new surveys now, MAYBE, one way to go is creating another survey exactly like the one you have, then populate the new one with the older data. If the fields of both surveys are exactly the same (except the new field you have added in the new survey), you can use the APPEND tool in GIS Pro to populate the new survey with old data.

Rama1356 · Answer

Hello,

I did talk to Esri team but prior to that I found a way to resolve the issue. In the XLSForm of Survey Connect, you need to set a proper instance name (setting sheet). I realized it has to be the name of one of your fields. I tried a dozen of other names and didn't work. Once I tried the name of my first field, it worked, and I was able to submit a new survey. I don't quite know what "Instance_name" does, but apparently, it makes a connection to the survey file.

Here you can see how I did it:

Survey Sheet:

Setting sheet:

As for the problem with extended publishing time, they noticed that there is an issue on their side, and they have opened a new case for that.

Hope it helps.