send error code 1000, then token required for same stuck survey

[LynnBerni]

I got a Send Error Code 1000 (see screenshot) for a survey that was submitted multiple times yesterday morning, but then got hung up in the outbox in the afternoon. 

I just tried to resend it today and am now getting a different Send error!  This time, all it says is Token Required. 

Any idea what's going on?

Thanks
Lynn

[LynnBerni]

Hi James,

Good to know for repeats editing, thanks!   If have one final question. I'm considering using repeats on one new form, to make data entry a little easier in the field. Specifically, our team of three field techs will visit multiple stream sites per day to collect various field parameters (weather, water chemistry, flow, etc.). Since their names and the weather in the past 24 hours would apply to all sites, I have that information in the first two questions, and then site-specific data in a repeat.

Given that repeats add complexity to the tables *and* can cause potential issues with the sending and editing of send forms, would you recommend that I eliminate the repeat in this case?  It's not like there are 20 questions that apply to all sites, just two. 

Thoughts?

Thank you,

Lynn

[JamesTedrick]

Fro the description you're providing, I could see an argument for either repeats or no repeats.  Certainly it does make it simpler in terms of data management, though will make the collection a bit lengthier.  I would try out without repeats and see if you have pushback from the collection personnel.

[LynnBerni]

Will do, thanks. This brings up another question that I've been wondering about. Is there a way to have a field autopopulate with the answer from the previous survey?? 

[JamesTedrick]

There are a couple of methods:

1) You can make a form a 'Favorite Survey' and load in the answers see Quick reference—Survey123 for ArcGIS | ArcGIS for more information

2) You can make a copy of a previously submitted survey from the Sent Box.

[LynnBerni]

But if I wanted only some of the fields to autopopulate....? In this case staff initials and weather past 24 hours....

[JamesTedrick]

Unfortunately, currently the entire form must be populated with previous answers.  

[LynnBerni]

Thank you so much for all your help today!  I want to circle back to two of your previous comments:

First, your note about editing repeats by using allowUpdates in the bind::esri:parameters column.

I saw this thread last week Copying "Repeats" to new surveys not working, and was wondering...is it true that if I use allowUpdates then I will need to make sure my repeats are named with an upper case letter? In case someone wants to copy the survey and retain all the repeats?

Second, you had initially asked if I was using Inbox to submit the surveys. I haven't looked into that yet. Since we have a number of part time field techs, and four field ipads, would it be wise to enable the Inbox so we can edit any surveys sent by any device?