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:
- Field operator opens a new survey form, completes the survey and takes a few photos as attachments.
- The form is closed and Saved for Later in the Outbox.
- The form is re-opened for editing, and saved as a Favourite Answers template, then closed again.
- A new form is opened and answers pasted from Favourites. This copies the photo attachments as well.
- Since new photos are required, the copied photo image attachments are Deleted from the new survey. This deletes the images from the device.
- Now, the original survey form referencing the deleted images have orphaned attachment records, since the attachments no longer exist. This can be seen by editing the form in the Outbox, and noting a reference to the attachment, but with no image visible.
- Trying to Submit this form results in the application hanging.
- We can salvage the collected form data by editing & deleting each orphaned attachment in each form. The form can then be submitted successfully; however the attachment images are irretrievably lost!
- This is clearly a data collection disaster.
- We can understand that some attachments may appropriately be saved as a favourite, eg a specification document relating to a specific asset type. It is therefore not a desirable option to prevent attachments from being copied over as Favourites.
- What is critical, however, is that attachments deleted from a survey form should only delete the link to the attachment, not the attachment itself!
- Another option would be to clone attachments copied over as Favourites, in which case deleting them would not affect the original.
- We were running Survey123 version 2.1.6 on Apple iPads running iOS 10.3.2. Surveys were authored in Survey123 Connect, Windows x86 version 2.0.41; however the nature of this problem would indicate that it is not a device- or OS-dependent issue. Since we have been using Survey123 extensively, we would appreciate it if ESRI could give urgent attention to a fix.
We have logged a support call with our distributor Eagle NZ but are still awaiting a response.