topic Re: Survey123 3.16.113 update makes Inbox updates null for select ones with esri field bind to integer in ArcGIS Survey123 Questions

Survey123 3.16.113 update makes Inbox updates null for select ones with esri field bind to integer

ChristopherCounsell — Fri, 09 Dec 2022 06:30:33 GMT

We have a survey with select_one questions and an esri fieldtype bind of integer (or small integer). The survey responses are edited via the field app inbox. After updating the survey123 field app to 3.16.113 these questions are populated in the Inbox, not changed, but when submitted, change to Null in the feature service. Works fine in 3.15.xx (values remain populated after submission)

Publish attached survey with Inbox and editing enabled
Submit records with values in the questions
Open the survey responses via the inbox. Note the values in the form. Submit without changing the responses. Reload the inbox. Note the values have gone null.

We believe the updates around 'BUG-000151353' in version 3.16.113 may have changed the way these values are handled.

We don't need the values as integer within the survey form itself (XLSForm bind and calculations not relevant) but do need to retain these values as integer in the feature service.

@IsmaelChivite is this an intentional change?

Re: Survey123 3.16.113 update makes Inbox updates null for select ones with esri field bind to integer

ZacharySutherby — Fri, 09 Dec 2022 19:01:52 GMT

Hello @ChristopherCounsell,

Are you originally submitting with "No" selected then switching to "Yes" in the Inbox? If so we have the issue where choices with 0 set as the choice name are nulling out on submission reported, please see this thread for more information. I have tested with the XLSForm passed along selecting "No" submitting > reloading in the Inbox, make no changes, resubmit with "No" still selected for all the choices and the values remain.

Re: Survey123 3.16.113 update makes Inbox updates null for select ones with esri field bind to integer

ChristopherCounsell — Mon, 12 Dec 2022 00:05:41 GMT

Thanks, that appears to be it. Will chase the bug number