topic Re: Survey123 version 3.12.274 Pulldata() functionality changes? in ArcGIS Survey123 Questions

Survey123 version 3.12.274 Pulldata() functionality changes?

BamJam — Thu, 25 Feb 2021 20:25:57 GMT

Hello Survey123 Community and @JamesTedrick or @IsmaelChivite

We have a form that has been in use for months that utilizes the pull data functionality to populate some fields in the form based on a barcode scan.

We have had several users call that are not getting data populated in those fields after a barcode scan. All our users are using iOS devices. We have isolated this issue to users that have version 3.12.274 of Survey123. We've verified that the necessary .csv file is in the media folder within the Portal item and that the data is properly populated in the file itself. Furthermore, users that are still on 3.11.164 are able to scan and get the necessary fields populated...even after updating the form itself. So, it seems to be an issue with version 3.12.274.

I have not been able to find any information on version 3.12.274. Is there a change in the pulldata() functionality?

Any help would be appreciated.

Thanks,
Brandon

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JamesTedrick — Thu, 25 Feb 2021 20:54:33 GMT

Hi @BamJam ,

Can you provide a sample of the form and lookup you are using? you can e-mail me directly at jtedrick AT esri.com

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

BamJam — Thu, 25 Feb 2021 21:34:17 GMT

Sent via email...

Thanks

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

ZacharySutherby — Thu, 25 Feb 2021 23:21:22 GMT

Hello @BamJam,

Thank you for passing along the XLSForm and associated CSV. I had tested on my end and narrowed the issue down to the column header missing for column A in the CSV. Once I added a column header (ID for example), saved the CSV, and refreshed the survey the pulldata() functions worked as expected.

The reason it broke with 3.12 was because we switched to a database approach for managing content, and since the column header was missing the CSV wasn't being imported into the database.

Thank you,

Zach

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

BamJam — Fri, 26 Feb 2021 01:15:44 GMT

Thank you guys for such a quick response and solution. We create the .csv file using Pandas in a python script. A simple fix for this was to set index=False when creating the .csv file, which eliminated the empty header in column A. Would not have known to apply that change without your testing and solution.

Thanks again!

Brandon

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

DustyJordan — Tue, 02 Mar 2021 06:48:05 GMT

EDIT: The problem seems resolved! Not sure exactly what was causing the issue unfortunately, but I simply opened the .csv tables I was having issues with, resaved them into the media folder, and updated/republished the surveys. Pulldata functions appear to be working once again. Sorry for the false alarm!

I'm running into the same issues as of today. The pulldata function no longer seems to be working on one of our forms. I noticed this occurred immediately after updating the Survey123 app to the latest version. The form still seems to function fine in Connect, but not the mobile app. I've checked my .csv and have no missing column headers. Any other ideas as to what is causing my pulldata function to fail?

This is pretty distressing as we use a multitude of Survey123 forms for our data collection and several of them make use of the pulldata function. I'm terrified that I'm now going to have to go through each form and figure out what's causing this.

Any help would be greatly appreciated. Thanks!

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JarrettCziesch1 — Tue, 02 Mar 2021 07:11:25 GMT

I am having the same issue with the pull data function for reverse geocoding on our public facing surveys.

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JarrettCziesch1 — Tue, 02 Mar 2021 07:27:19 GMT

I simply renamed the column A header and re-saved, then published it again (just like your description) and it appears to be working with the pull data functions again. fingers crossed.

Thanks,

Jarrett

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JarrettCziesch1 — Tue, 02 Mar 2021 07:54:08 GMT

Nope. public facing surveys are not still working with pull data functions within the .csv. I noticed the new version 3.12 does not allow JavaScript functions for public surveys either.

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

ZacharySutherby — Tue, 02 Mar 2021 17:23:39 GMT

Hello @JarrettCziesch1,

Please note JavaScript functions do not work with public surveys. This isn't a new limitation of 3.12 this has been a limitation since their implementation at 3.10. Please refer to the known limitations section of the JavaScript functions documentation for reference: https://doc.arcgis.com/en/survey123/desktop/create-surveys/pulldatajavascript.htm#ESRI_SECTION1_2A1B3F6B4F4741E9BC1BE519E671E565

Please refer to this link for the ArcGIS Ideas post for supporting JavaScript functions on public surveys and the associated ENH number.

As for the pulldata using a CSV not working please check the CSV to ensure none of the column headers use any of these reserved words: https://www.sqlite.org/lang_keywords.html

If none of the column headers use any of those reserved words would I be able to obtain a copy of the survey and the CSV for testing on my end? Please feel free to send it to ZSutherby@esri.com and I'll be happy to take a look into the behavior.

Thank you,

Zach

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

ZacharySutherby — Tue, 02 Mar 2021 17:21:39 GMT

Hello @JarrettCziesch1,

For reverse geocoding on public facing surveys is the issue specific to the Webform, Field App, or both?

If the behavior is present in the Webform please open the F12 developer tools in your browser and select the Network tab. When you try to run the reverse geocode if you select the request that is being send to the geocode service is the response "token required"?

Thank you,

Zach

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JarrettCziesch1 — Tue, 02 Mar 2021 23:07:28 GMT

Hello Zachary,

Token is required and all headers are not reserved.

Jarrett

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JarrettCziesch1 — Tue, 02 Mar 2021 23:08:24 GMT

{
"code": 499,
"extendedCode": -2147220966,
"message": "Token required but not passed in the request.",
"details": [
"Token required."
]
}

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JarrettCziesch1 — Tue, 02 Mar 2021 23:14:52 GMT

I put in a notice to our server administrator. From what I gathered, the survey should be non secured.

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

RyanDay1 — Thu, 04 Mar 2021 15:10:37 GMT

We also are experienced problems with pulldata(...) in a survey we were building.

It seemed that after the latest app update the csv has different limitations on the column names.

We had spaces in the column headers and special characters like parenthesis and percent. Which previously worked, but after update the pulldata(..) was not working.

After cleaning up the columns in the csv to more 'database friendly' header names the pulldata(..) in the mobile app started working again.

Note the survey123 connect app continued to work with spaces and special characters in the names.

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

KaitlynAbrahamson — Wed, 10 Mar 2021 18:56:29 GMT

I am having the same issue and am not sure how to get my pulldata to work now after the update. I am now using Survey123 3.12.229. All my pulldata columns are lowercase and without spaces. What else can I do to get it to work? Attached is my media file for the pulldata.

Thanks!

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

JarrettCziesch1 — Wed, 10 Mar 2021 19:10:37 GMT

Hi there, I assume you use them for reverse geocoding? if your form is
public facing the pulldata functions will not work. This happened as a
result of the new release. JS functions will not work with public facing
firms as well. I am currently researching ways to develop something to
compensate for this but may need to use something different.

The only option to use pulldata functions for reverse geocoding is to
provide a profile for either a group or individuals.

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

KaitlynAbrahamson — Wed, 10 Mar 2021 19:14:42 GMT

Thanks!

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

KaitlynAbrahamson — Wed, 10 Mar 2021 19:35:11 GMT

Sorry, I meant to post this under the main question. Thanks for trying to help, though!

Re: Survey123 version 3.12.274 Pulldata() functionality changes?

ZacharySutherby — Wed, 10 Mar 2021 19:56:12 GMT

Hello @KaitlynAbrahamson,

The reason for the issue is because column N in the CSV is missing content. If you move the contents from column O (areaformula) into column N then the CSV should work properly.

This is related to the original issue where empty column headers prevent the CSV from being imported into the database.

Thank you,

Zach