Working with Versioned Data and Feature Service Sync Gary MacDougall Russell Brennan

Feature Service Sync Sync is a feature service capability - Added at Allows you to… - Get a local copy of the feature service data - Make edits locally even while offline - Sync when online Used by Collector for ArcGIS, Runtime SDK, …

Data Requirements and Sync Data can be either - Non-versioned with Archiving + GlobalIDs or - Versioned + GlobalIDs Use versioned data when - The data model requires versioning (e.g. geometric networks editing) - Versioned workflows are required (e.g. long transactions)

Versioned Data and Sync Workflows Read-Only Services - Keep reference data up to date on your device Read-Write Services - Allows you to sync edits made in the field - Added versioned data support for read-write services at Versioned created for each… - Downloaded map (Default) - User

Versioned created for each downloaded map Published Version Download Map User_Service_ID1 User_Service_ID2

Versioned created for each user Published Version Download Map User_Service Sync

Synchronization Workflows (On-premises Services) Author Map Publish Service View, Query Edit Synchronize Download ArcGIS Desktop Create Replica Prepare Maps

Workflow 1 – Data Maintenance Author Map Publish Service (read write) View, Query, Edit Download ArcGIS Desktop Prepare Maps Sync Remove Map

Demo Download maps for data maintenance

Workflow 2 – Valve Inspection Project Make Updates Download ArcGIS Desktop Prepare Maps Sync FWQA Version

Workflow 2 - Download maps for a short duration project Author Map Publish Service (read write) Make Updates Download ArcGIS Desktop Prepare Maps Sync Remove Map Proj Version

Demo Download maps for a valve inspection project

Workflow 3 – Download read-only maps Syncs from the published version (e.g. default) Publish Service (read only) View, Query Download ArcGIS Desktop Prepare Maps Sync

Help Reference Offline maps and versioned data - Long URL: - versioned-data.htm versioned-data.htm - Short URL: Demo reconcile/post script - Long URL: - reconcile-post-after-sync.htm reconcile-post-after-sync.htm - Short URL: -

Setting up Feature Services for Offline use On premise feature service must be preconfigured for sync - All layers must have a global ID AND - All layers or tables in the service must be non-versioned with archiving enabled OR - All layers or tables in the service must be versioned Data with attachments must use global id based relationships - Use migrate relationship class

Publishing with versioned data With versioned data, versions are created from the published version for individual clients when maps are taken offline. When a client syncs, edits are applied to this version. - Ensures scalability when many clients are syncing concurrently - Because not all clients are syncing with the same version This means that additional back office processes are required to reconcile and post edits from these versions into the feature services’ published version These processes allow others to see the synced edits and allows the offline clients to get the latest changes from the service on the next sync

Working with offline maps and versioned data With versioned data when a map is taken offline a version is created from the published version for individual clients. When a client syncs, edits are applied to this version. Two options are provided when publishing to allow the admin to choose how versions are created. - Create a version for each offline map (default) - Create a version for each user

Create a version for each offline map (default) With this option, a version is generated from the published version each time a map is taken offline. The version name is based on the user name + service name + timestamp - E.g. Bob_NetFS_ If a map is taken offline multiple times (e.g. from more than one device), different versions are used when the user syncs from each device. In this case, one device will not see edits from the other device. New offline maps will be current with the published version. As offline maps are removed, their versions can be reconciled, posted, and deleted.

Create a version for each user In this case a version is generated for each user that takes a map offline. Each version is specific to the user, the name is based off the user + service name - E.g. Joe_ValveFS. If a user takes the map offline multiple times (e.g. from more than one device), the same version is used when the user syncs from each device. All devices will see edits from the other devices. New offline maps will only be up to date as the last time the user’s version was reconciled. A user version will remain as long as the user has at least 1 offline map.