topic Re: send error code 1000, then token required for same stuck survey in ArcGIS Survey123 Questions

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

LynnBerni — Fri, 06 Apr 2018 21:22:41 GMT

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

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

JamesTedrick — Fri, 06 Apr 2018 21:36:56 GMT

The token required indicates you may need to sign out/sign in again - while Survey123 does refresh the login token, there are circumstances where it can express and not be renewed. On the duplicate key issue- is this survey populating values via URL or is Inbox set up?

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

LynnBerni — Fri, 06 Apr 2018 21:45:09 GMT

ok, good to know about the token. I hadn't yet seen that. I have not set up Inbox so I guess via URL

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

JamesTedrick — Fri, 06 Apr 2018 22:01:58 GMT

Hi Lynn,

The URL/Inbox are a couple of methods outside of the normal way to submit data (they're not an either/or option); they happen to be the most likely way a duplicate global id can come about (they're different ways to programmatically load data from outside Survey123 into a form, which is the easiest way to create a duplicate globalid).

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

LynnBerni — Fri, 06 Apr 2018 22:08:18 GMT

ok, i signed back in and am now getting that same error code 1000. I built the survey in Connect (v2.6.6) and have the feature service that was created in my agol.

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

JamesTedrick — Fri, 06 Apr 2018 22:13:32 GMT

Yes, I would expect that error to still be present. Does your survey have a globalid question in it? Can you share the XLS file so I might try to duplicate the error you are seeing?

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

LynnBerni — Fri, 06 Apr 2018 22:35:53 GMT

Yes I guess there are globalIDs because i have repeats. Oh boy, could this be related to the fact that I made a few changes to the XLSX, but then when I tried to publish it says there is no WEATHRNOW field? I moved (cut/insert cut cells) the WEATHRNOW field into the repeat, so I don't get why it's saying it's not there. So the spreadsheet is actually a little different than the survey that won't go thru. Argh, this is a mess. But if I didn't publish it shouldn't matter right?

I don't see where to attach a file (?), so here's a link to the XLSX, Field Parameters v2.xlsx - Google Drive

Thanks!

Lynn

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

JamesTedrick — Fri, 06 Apr 2018 22:43:16 GMT

Hi Lynn,

When storing records in the database, repeats are stored in a separate table (as a related record); a field in the repeat called WEATHERNOW would be different from a field outside the repeat called WEATHERNOW.

Given that you have a repeat, I'm wondering if you opened a survey from the sent box, either to edit or copy into a new record? If you did, I could see that also leading to this situation.

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

LynnBerni — Fri, 06 Apr 2018 22:50:34 GMT

Of course, that totally makes sense...forgot the the related table!! It's very possible that the survey was opened from the sent box and and "edit and resend" was attempted (we're all still learning how to use Survey123). Which, i've noticed, doesn't work for data in the repeats. You can reopen the survey, but only data *not* in a repeat is editable.

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

JamesTedrick — Mon, 09 Apr 2018 18:04:52 GMT

Hi Lynn,

On editing repeats - we normally disallow that by default, but it can be enabled by providing the allowUpdates=true statement in the parameter column for the repeat.

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

LynnBerni — Mon, 09 Apr 2018 22:22:25 GMT

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

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

JamesTedrick — Mon, 09 Apr 2018 22:25:58 GMT

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.

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

LynnBerni — Mon, 09 Apr 2018 22:31:24 GMT

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??

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

JamesTedrick — Mon, 09 Apr 2018 22:35:39 GMT

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.

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

LynnBerni — Mon, 09 Apr 2018 22:51:56 GMT

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

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

JamesTedrick — Mon, 09 Apr 2018 22:54:25 GMT

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

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

LynnBerni — Mon, 09 Apr 2018 23:22:33 GMT

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?