topic Re: 10.3.3 false sync in ArcGIS Collector Questions

10.3.3 false sync

danbecker — Thu, 17 Sep 2015 21:14:16 GMT

10.3.2 would sync related data and/or feature data perfectly fine, no changes to the services were made.

Upgrade to 10.3.3 Collector on iOS.

Collect new related data and/or feature then sync over wifi.

Rest Endpoint: Replica page last sync date is not changed.

Obviously the data is not in the SDE geodatabase.

Shouldn't Collector (or ArcGIS Server) throw an error? I'm not seeing anything.

Anyone else have this issue?

Re: 10.3.3 false sync

danbecker — Fri, 18 Sep 2015 13:50:28 GMT

The problem looks to be gdb versioning; for anyone else experiencing this issue, archiving solved the problem.

The gdb also has editor tracking and attachments enabled on a table.

Collector 10.3.2

SDE Geodatabase (SQL Server Express 2012), registered as versioned

Default version added to map, published as Server 10.3.1 sync enabled feature service

Feature service added as item to AGOL, credentials stored with service item

Added item to webmap, saved

Adding feature and/or related records worked great both online and offline

Upgraded to Collector 10.3.3

Used the same web map as above

Adding feature and/or related records worked online, NOT offline

Sync would appear to be successful, but "last sync" on service endpoint/replica remained unchanged

Data never made it to SDE geodatbase

Collector 10.3.3

Unregistered the SDE Geodatabase as versioned

Enabled archiving on the SDE Geodatabase

Created new map document

re-published as Server 10.3.1 sync enabled feature service

Feature service added as item to AGOL, credentials stored with service item

Added item to new webmap, saved

Adding feature and/or related records worked great both online and offline

Re: 10.3.3 false sync

ScottPrindle — Fri, 18 Sep 2015 23:34:46 GMT

Hey Dan,

When you were synchronizing your disconnected dataset, were you checking the child version it produced for the edits? Based on the versioning workflow, each disconnected dataset will be associated with a new version in the database when it is downloaded. When synchronizing your offline edits, they will be pushed to the database but not to the parent version (ex. DEFAULT or VersionForFeatureService). Please take a look at the link below for more information on working with Collector, sync, and versioned data:

http://server.arcgis.com/en/server/latest/get-started/windows/tutorial-create-offline-maps-with-versioned-data.htm#ESRI_SECTION1_16C42328112046E8BFCF9E49E49E7872

Re: 10.3.3 false sync

danbecker — Mon, 21 Sep 2015 15:19:11 GMT

thanks so much Scott! That was exactly the case; a new version gets created when the map is taken offline, then the changes are saved in that version, which has to be reconciled/posted back to default.
Do you know, was this recently added in 10.3.3?

Regardless, everything is working as-expected; next time I need to dig deeper into the docs b4 posting.

Re: 10.3.3 false sync

ScottPrindle — Mon, 21 Sep 2015 16:35:25 GMT

Hey Dan,

Sync was introduced on ArcGIS for Server at version 10.2.1 with support for archiving, but support for versioning was not introduced until 10.3 I believe. Either method should work for synchronization, but if your data is versioned you will be presented with these additional steps to get your data reconciled/posted back to DEFAULT.

No worries on the topic, it's an interesting one to bring up. You can read a little more about sync with versioned data here: http://server.arcgis.com/en/server/latest/publish-services/windows/offline-maps-and-versioned-data.htm

One important setting that is discussed at that link is the "Create a version for each offline map/each user" option. This will let you choose whether each download or each signed in user that downloads the data will generate a new version. Choosing "each user" can help clean up your database, only creating new versions for each user rather than every disconnected dataset.