ArcPad 10.2.2 Feature Service Fails with Editor Tracking Enabled
BUG-000085108 - Incorrect synchronization results in ArcPad 10.2.2 when Editor Tracking is enabled
Hey there, not sure of a better place to add this. Just like the title says. We upgraded and had some very unusual behavior syncing including those using mobile devices having AP crash after syncing and changes not being pulled own. The desktop version of AP had odd behavior as well. Just posting this as a heads up.
The ArcPad support services team was (as usual) great to work with in diagnosing this issue. But it does represent a bit deal to our organization. We had a couple of options in front of us but none were ideal. The fixes/upgrades to 10.2.2 are certainly worth staying at that version.
So my workaround is going to be authoring projects for our users which have Quick Fields in place which will populate fields for user name and the date. Even though I'll have to modify the schema of our data to support these new fields, there are certain advantages to this method. Anyone who's worked with with editor tracking knows that if you've had to load data or work with replicated data, you know that Editor Tracking isn't bulletproof in terms of capturing the data creator permanently. As a bonus, we'll be collecting X & Y data at the time of data creation too. Wish I had known about this before.
Hope this saves someone a bit of trouble!