To all who posted in this forum, Matt and I have been working together on this and we have determined this is a bug:
NIM103949 - [Point features are not saved in ArcPad 10.2.1 when utilizing a workflow with a custom applet and closing ArcPad within 20 seconds.]
I brought the issue to the attentions of the dev team in Redlands and they believe the edits aren't saving right away due to individual processes that haven't been able to complete and store the edits until that time limit has passed. In Matt's case, we think it is due to the fact that multiple AXF files are being used in the applet and because each action made against a different AXF is a different process on the back end.
The workaround for now is to let your users know to leave the application open for more than 20 seconds so all the edits get saved.
Thanks,
Sarah
Hi,
I know this is a little late to the game on posting, but has anyone made progress on this issue. I am currently dealing with this issue and it is starting to cause major stoppages in work flow. I have field crews surveying poles points for routing on a project. Through a custom form they collect information at a pole and report any issues. My form uses custom scripts to pull information from background AXF. Most of the time the points are appearing as they should, but I have had entire days or weeks work disappear after the surveyor packs up for the day. I know the surveyors were at the points I need due to pictures being taken and other files created at the same time the point is collected. I have even had partial surveys disappear when the surveyor half finishes and comes back to it the next day.
Any body have any easy work around that would prevent arcpad from losing my point data?
Hi Derek,
Did you ever find any solutions to your problem? One of our Juno units has been experiencing data loss as well. It's very similar to what you described. Field crews are out all day collecting points, lines, and polygons for an archaeological survey, and then occasionally, when they close the map, *poof*. The entire day of data is simply gone. I'm not sure if the problem is related to the bug mentioned above or not. I'll have the unit in my hands in a few days, and will try to reproduce the behavior.
I was told several months ago by Esri Support that the user must wait 30 seconds before closing ArcPad to ensure the last edit (to the axf or to the apm) is saved. So I don't think the problem has been resolved, but there is a known work-around.
Hi Ingrid,
I was wondering if this had something to do with what we are seeing. But the fact that the users continuously record data for long periods of time without closing map or letting the unit hibernate, makes me believe that the problem lies elsewhere. It is good to know of this limitation, however, and I'll make sure our field crews aren't shutting down the maps prematurely.
Thanks.