We have come across a critical flaw in the application which has resulted in the irretrievable loss of field data – obviously a major concern. The problem was noticed when Survey 123 hung up when submitting completed surveys, and had to be killed and re-opened – but the problem kept recurring.
On investigation we have identified the cause of the problem, which exposes a critical flaw in Survey123. A sample workflow is as follows:
Comments
We have logged a support call with our distributor Eagle NZ but are still awaiting a response.
Hi Nick. Thanks very much for the detailed notes. You raise a critical issue (as it involves data loss) and your suggestions for resolution are very useful. We will discuss how to better approach this. Thanks.
Hi Ismael,
Have you made any further progress with this
Thanks
Nick
Hi Nick,
In the 2.4 release, the behavior of Favorite Answers was changed to not carry over images into the new form- this should address this issue.
I see this issue was first raised in November 2016 by Jonathan Pendleton - but reported solved going from version 1.8 to 1.9!
The underlying issue seems to be that attachments are managed by a composite 1:Many relationship class, whereas the scenario described is actually a Many:Many association between attachments and surveys. Having a junction table between the image attachment table & parent table would allow the association record to be deleted while preserving the image saved as a blob in the attachment table. This would be a more elegant solution than cloning copied images, which could blow out data storage and upload bandwidth requirements and result in unnecessary duplication of images.