topic Re: Null integers reported as 0 in ArcGIS Survey123 Questions

Null integers reported as 0

Trippetoe — Tue, 17 Oct 2017 22:12:03 GMT

Whenever we have a data type of integer that has a null value reported on the survey (for fields that are not required), the actual data value that is stored for the field is 0. Is there some setting or some such that we need to set so that null values are reported as null instead of 0?

Based on some of our older data, this is a new 'feature'. We have records from older surveys where null integers are indeed reported as null instead of 0.

Thank you.

Re: Null integers reported as 0

BrandonArmstrong — Tue, 17 Oct 2017 22:54:48 GMT

Hi Tom,

My I ask which version of Survey123 you currently have? Also, if possible, can you share an XLSForm which exhibits this behavior?

Thank you,

Brandon

Re: Null integers reported as 0

Trippetoe — Tue, 17 Oct 2017 23:07:54 GMT

Hi Brandon.

Thanks for your reply.

We recently updated to 2.4.72 - windows and android. I can't say absolutely that the problem started with the upgrade but it seems coincidental.

If you give me your email address, i'll send a copy of the xlsform. I do know the Survery123 team has a copy of the form as they were helping us with some debugging efforts in the last 10 days or so.

I am going to see if i can find an older version of the app to test against in the meantime.

Re: Null integers reported as 0

Trippetoe — Tue, 17 Oct 2017 23:20:38 GMT

Hi Brandon.

I dug up an older version of Survey123, version 2.3.29. When i submitted a survey using that version, 'null' integers are displayed as null/empty - not as 0. THis behavior does seem to be related to the version of Survey123.

Re: Null integers reported as 0

BrandonArmstrong — Mon, 23 Oct 2017 17:35:23 GMT

Hi Tom,

I was able to reproduce the issue that you mentioned above, and have logged a defect in technical support on your behalf. The defect is listed as the following...

BUG-000109011 - Survey123 for ArcGIS field app does not prevent blank required integer type questions from being sent which results in 0's being recorded as the submitted value.

One thing to note, is that a blank integer question should still reflect a blank value when not listed as 'required' and not within sequential iterations of a 'repeat'. The behavior seems to occur when a value is initially placed in the integer question, and then removed, or when an integer question is present within a repeat. Please let me know if you desire any further clarification.

Re: Null integers reported as 0

Trippetoe — Mon, 23 Oct 2017 18:02:48 GMT

Hey Brandon.

Thanks for looking into this issue. I really appreciate your help and persistence.

Re: Null integers reported as 0

FinnianO_Connor — Mon, 23 Oct 2017 22:41:46 GMT

Hi BArmstrong-esristaff‌, just to add that I am also observing this behavior when data is entered through a web browser and not the field app. A zero value is stored in all fields that are defined as an integer if a user does not enter any data. This happens without ever entering a value for the field (different to what you describe where an initial value is removed or the integer is within a repeat). Quite a problem for some of my forms as zero is a valid answer (as is a null value) so the data being stored is misleading.

Cheers,

Finnian

Re: Null integers reported as 0

BrandonArmstrong — Tue, 24 Oct 2017 16:31:26 GMT

Hi Finnian,

I did test, and was able to reproduce the issue that you mentioned with the web form. I will go ahead and log a separate defect for this and post a reference to it below.

Re: Null integers reported as 0

BrandonArmstrong — Tue, 24 Oct 2017 17:23:49 GMT

BUG-000109060 - Surveys submitted via Survey123 web form are reflecting 0's as the value for integer questions left blank

Re: Null integers reported as 0

FinnianO_Connor — Tue, 24 Oct 2017 21:43:23 GMT

Thanks for the update Brandon

Re: Null integers reported as 0

JosephAlberts — Fri, 12 Jan 2018 19:14:02 GMT

This appears to still be an issue as of 2.5, correct?

Re: Null integers reported as 0

MartinDe_Las_Heras — Thu, 15 Aug 2019 16:13:03 GMT

Hello,

Is this still a known bug? I am currently experiencing the same issue, using Survey123 Connect 3.5.166. I'm getting null values when the survey is submitted from the web browser. The field app defaults to 0, but I have a survey that needs to be filled from the web browser. Any help is much appreciated.

Re: Null integers reported as 0

BrandonArmstrong — Thu, 15 Aug 2019 17:33:32 GMT

Hi Martin,

The issue(s) mentioned in this thread have been resolved. Please share your XLSForm if you are encountering inconsistencies in submitted values between the field app and web app. Also provide us with the version of the field app that you are using when submitting the survey.

Best,

Brandon

Re: Null integers reported as 0

MartinDe_Las_Heras — Thu, 15 Aug 2019 17:49:49 GMT

Brandon,

Thanks for the quick reply. I'm using version 3.5.177 of Survey123 on my cell phone. On the XLSForm I have set the default to 0 for these fields, however all these fields/questions are conditional, only appearing on the form when the answer is 'yes' on the previous question.

The issue caused by these null values is that when any of the 4 calculation fields I have on the XLSForm encounters an empty value, it returns NaN as a result. I must be doing something wrong, I have just recently started using Survey123 Connect instead of the web designer.

Please find form attached.

Thanks,

Martin

Re: Null integers reported as 0

BrandonArmstrong — Thu, 15 Aug 2019 22:02:30 GMT

Hi Martin,

The behavior that persists when submitting using the web app is actually the correct behavior. When a question is is not relevant, even a default value will not and should not be stored in the data. Only upon becoming relevant should the value be persisted.

We have a defect regarding the behavior that you are encountering with the field app, where default values are being populated even when the question has not yet become relevant. We are hoping to be able to address this with our next release.

The logic of your form may need to be reconsidered so that the expected behavior (default values not being persisted until the question becomes relevant) does not surprise you when it is fixed in Survey123 Connect and the field app.

Best,

Brandon

Re: Null integers reported as 0

MartinDe_Las_Heras — Fri, 16 Aug 2019 12:53:00 GMT

Hi Brandon,

Thank you for taking a look at my XLSForm and clarifying that! I just wasn't sure which behavior was the correct one. I still need these questions not to be shown unless the user replies 'yes' on the previous question, so I'll adjust my calculation fields so they convert any nulls to zeroes.

Thank you for your help!

Martin

Re: Null integers reported as 0

Anonymous User — Mon, 19 Aug 2019 10:38:07 GMT

Hi Martin,

The issue with default values populating when a question is not relevant has been fixed and you can test it out with latest 3.6 beta builds available on EAC. The latest version to test with is 3.6.100. Please let us know your feedback.

Regards,

Phil.