We've had a number of people have the situation where they have gone to submit surveys and S123 says it has failed, they submit again, then we find duplicate records in the feature layer.
We have a feature service hosted on AWS servers and registered on AGOL.
It's not repeatable and I haven't had it happen on any of my tests, but we've had a number of people in different areas had it happen.
We currently rely on a scheduled task to look for duplicates (using S123's unique id field).
It may have to do with photo size and internet connectivity and we've reduced our photo size to reduce the risk.
Has anyone else experienced this?
Short answer, yes, this issue has been experienced by other users and is reproducible with surveys with attachments when the network connection is unstable or slow. Currently the survey record is uploaded first, and then the attachments uploaded. If the attachments fail due to network connection loss, the survey record will already exist in the feature service but with no attachments. When the survey is sent again, it will create a duplicate with the attachments. To avoid this issue, surveys with attachments should be uploaded when the network connection is stable and fast and as you suggest using a smaller photo size is recommended.
We also recommend ensuring that all users have the latest version of the app installed, as we are constantly working on improving this issue and other app related bugs. We currently have a feature enhancement to resolve the upload failure bug, and hope to implement this is a future release.
Would you be able to share either logged Bug's or Enhancement information? We could then track this with Esri Support Services, and for our own records. Thanks, Phil!
Changes were implemented in version 2.6 and 2.7 of the app to improve the handling of uploading attachments and reduce the occurrence of duplicate survey entries if attachments fail. There was no specific external support bug or enhancement request for this issue, it was implemented as part of our continuous improvement and feature releases. Note that if you are using ArcGIS Online and the last version of the app, you will be using this new method for upload, however if you are using Portal it will depend on the Portal version and whether you have federated services. The feature requires the use uploadids capability to be set to true and supported by the Portal.
Yes, this issue was fixed as described above, the process of how attachments are uploaded is the same for parent layer or repeats. The attachment is uploaded first, then the feature, and then they are related to each other. That way if there is a failure you will not end up with duplicate attachments to the same feature.
Are you seeing an issue? If so can you share more details about it and the workflow being used?