topic Re: Automatically Update Coded Values in ArcGIS Survey123 Questions

Automatically Update Coded Values

TonyDaSilva1 — Wed, 17 May 2017 20:32:06 GMT

Hi, I was wondering if I am able to write a script to update the Survey123 Form Coded Values periodically because they are time sensitive to changes?

However I noticed that my developer application token is forbidden at the following address

https://www.arcgis.com/sharing/rest/content/users/islgispub/{accountId}/items/{ServiceId}/update

Re: Automatically Update Coded Values

JamesTedrick — Wed, 17 May 2017 21:53:14 GMT

Hi,

You should be able to write a script to rezip the survey file and update. One thing to note while testing - the update resource is POST only, if you're experimenting you should use a program like POSTMAN first to get everything correct manually.

Re: Automatically Update Coded Values

TonyDaSilva1 — Wed, 17 May 2017 23:45:04 GMT

Thanks for the quick reply.

I have already written a script to update and re-zip it and send it to the /update endpoint using POST but even with a token it is giving me a 403 forbidden error.

Am I missing something?

var zipfile = File.ReadAllBytes(ZipPath);
var thumbfile = File.ReadAllBytes(ExtractPath + "\\esriinfo\\Survey.png");
var postData = new MultipartFormDataContent();
postData.Add(new StringContent("pjson"), "f");
postData.Add(new StringContent(""), "snippet");
postData.Add(new StringContent("Survey"), "title");
postData.Add(new StringContent(Token), "token");
postData.Add(new StringContent("Form, Survey123, Survey123 Connect, xForm"), "typeKeywords");
postData.Add(new ByteArrayContent(zipfile, 0, zipfile.Count()), "thumbnail", ServiceId + ".zip");
postData.Add(new ByteArrayContent(thumbfile, 0, thumbfile.Count()), "thumbnail", "Survey.png");
var response = client.PostAsync(UpdateUrl, postData);

{[error, {
"code": 403,
"messageCode": "GWM_0003",
"message": "You do not have permissions to access this resource or perform this operation.",
"details": []
}]}

Re: Automatically Update Coded Values

JamesTedrick — Thu, 18 May 2017 15:35:50 GMT

The token should be a parameter in the UpdateURL component, not posted in the form data (token authorization happens before processing of form data)

Re: Automatically Update Coded Values

TonyDaSilva1 — Thu, 18 May 2017 21:27:22 GMT

I am replicating what Survey123 form data is using and Survey123 is providing the token in the form data.

Also, if I grab a Survey123's token that it generates and use it, it returns successful.

Re: Automatically Update Coded Values

TonyDaSilva1 — Fri, 26 May 2017 20:51:13 GMT

I think I have found my answer:

Limitations of App Login | ArcGIS for Developers

Applications cannot create, update, share, modify, or delete items (layers, files, services, maps) in ArcGIS Online or Portal for ArcGIS.

Am I correct in thinking that a web service cannot automatically updated coded values of a Survey123 form?

Re: Automatically Update Coded Values

JamesTedrick — Tue, 30 May 2017 15:53:11 GMT

Oh- I missed completely that you were using an application ID/secret token instead of a username based token. Yes, that is the issue.

Re: Automatically Update Coded Values

TonyDaSilva1 — Tue, 30 May 2017 23:00:55 GMT

Is there a way around this, we would like to synchronize our data with our forms without manually updating them every time the data changes?

Re: Automatically Update Coded Values

JamesTedrick — Tue, 30 May 2017 23:13:25 GMT

The easiest way to do that would be to generate a long-life user token and use that instead of the app login.

Re: Automatically Update Coded Values

TonyDaSilva1 — Tue, 30 May 2017 23:28:05 GMT

Okay thanks, that's what i figured i would have to head towards... I've been reading up on OAuth2, is it possible to have the token refresh itself as 2 week expiration is not ideal ?

Re: Automatically Update Coded Values

JamesTedrick — Wed, 31 May 2017 15:59:16 GMT

Absolutely - take a look at the 'server-based workflow'. As part of the token generation process, a the expiration and a refresh token accompanies. You would have your script store these locally and check the expiration time to now; if less than your criteria, you exchange the refresh token for a new token. The documentation mentions a 'permanent' token; be advised that capability will be removed in an upcoming ArcGIS Online release.

You may have to start this process manually by using, manually constructed urls, a local web server that won't attempt to process the codes or tokens as your redirect_URI & Postman or curl to complete the authorization code > token and initial (short life) token > long life token exchanges.