Hello, we're still having troubles with quick capture. It sometimes sends duplicate values within 2-3 seconds. It just captures one incident twice, with completely same values, but created_date differs by 2-3 sec (user sends it from device just once). Does anyone know what can it be caused by? Thanks for your help. Jane
Solved! Go to Solution.
Can you provide some more info on this:
- What platform are you using to run the app?
- How are you connecting to the internet (4G - Wifi) and does this change?
- What is the autosend interval set to? Or are the users sending manually?
- Do the features have attachments?
- How regularly are you seeing this issue?
It is possible that a feature is sent twice if the app does not get a successful response from ArcGIS when it uploads a feature. This can happen when network connectivity is patchy and the user is on the edge of network/wifi coverage.
I'm happy to work with you to investigate this further if this does not sound to be the cause.
I hope we have stable 4G connection within the city, while the officers are moving just around the city. But of course I can't say this with 100% certainty.
Thanks a lot for your help. With captured data we have connected subsequent agenda so it is important to us not to have unnecessary duplicities in data.
I am having this exact same issue with quick capture. The points with pictures are sending two points for each entry. One of the points contains the attachment and the other point contains all the data without a picture.
We are also experiencing the duplicate records and are currently conducting aerial surveys using the app. I just checked to see if the latest release was out but don't see it. Do you have a date for when it will be released?
Thanks Jonathon! We've downloaded the update and hopeful it will fix the repeats. It looks like besides the repeat issue we also had some sync duplicates. We are working offline and so it looks like there are multiple CreationDates for some of the points as well. When the surveyor is syncing there likely isn't the best internet connection so maybe the points tried to sync a couple of times is all we can figure since they are the same geometry/fix time. I'm so glad we lucked out on the timing for this hotfix.