Hi Kal, I am using the humanitarian server for a study in India and my enumerators are facing the same issue. Could you please help me to understand (1) why this is happening and (2) the quickest and easiest solution?
We are using Enketo on Chrome browsers on Android devices, not the Kobo Collect app. I was given to understand that survey data is stored in the cache of the browser, and so clearing it is not advisable as one would lose other as yet unsubmitted drafts.
The enumerators have to travel long distances to collect the data and the lack of saving capability to causing significant difficulty – kindly send help asap!
I can ask them to try this, but our main issue is not submitting the draft – it is that the draft does not seem to be saving. This means that if the enumerator logs out, we may lose the unsaved input and therefore won’t be able to try re-submitting. Is the assumption that once they re-login, Kobo will show the ‘an unsaved record was found’ message and allow them to re-load the unsaved input?
In this case, it doesn’t work – it doesn’t have to do with the draft name typed out by the enumerator. We have tried changing that and unfortunately we’re still getting the same error message. Logging out and in again doesn’t seem to be working for everyone either.
@Kal_Lam – any other suggestions for how to fix this?
Do you use a calculation for the instanceID (in settings)?
Do the enumerators (or the system) write this case ID?
Could you send a screenshot of the case navigation window on the left? If possible together with the new entered case window part.