My form is configured to capture the *username *field automatically.
This runs fine most of the time, but recently I received a single
submission that had no username populated. (Initially picked up this was null
in the published json, but also confirmed in Aggregate that it is missing).
All other info in the form appears to be populated fine.
The form is not accessible without a username and password (I confirmed
this again by trying to access oursite.appspot.com/formList from a
browser), so it couldn't have been completed before username and password
were entered in Collect.
Do you have any idea what could cause this, or have you seen this happen
before?
username and email are populated upon beginning a new form.
They are not revised to reflect the configured values at the time of
transmission to ODK Aggregate.
i.e., this can happen if the form is begun before the URL and username /
password are configured to interact with the server. Or if the username is
removed and then later added back in.
ยทยทยท
On Fri, Jan 13, 2017 at 1:01 AM, Andrew wrote:
My form is configured to capture the *username *field automatically.
This runs fine most of the time, but recently I received a single
submission that had no username populated. (Initially picked up this was null
in the published json, but also confirmed in Aggregate that it is missing).
All other info in the form appears to be populated fine.
The form is not accessible without a username and password (I confirmed
this again by trying to access oursite.appspot.com/formList from a
browser), so it couldn't have been completed before username and password
were entered in Collect.
Do you have any idea what could cause this, or have you seen this happen
before?