[10/05/2025]

Introduction

This guide provides step-by-step instructions for enabling Geodatabase Sync and exposing the Create Replica operation on an ESRI Feature Service. When complete, your service will support offline/replica workflows used by FieldVision and seamless data exchange with CoreVision.

Important: Sync and Create Replica are available only on Feature Services (the /FeatureServer endpoint). A Map Service (/MapServer) cannot be sync-enabled.

Supported ESRI Software Versions

• ArcGIS Enterprise: 10.2+ (feature access), latest recommended
• ArcGIS Server: 10.2.2+ (Sync capability), latest recommended
• ArcGIS Online (AGOL): Current
• ArcGIS Pro: 2.x or later (publishing recommended)

GIS Data Hosting

• ArcGIS Enterprise / Server: On-prem or cloud, token/enterprise auth
• ArcGIS Online (AGOL): Hosted feature layers, OAuth

What We Require

• Feature Service URL (ends with /FeatureServer)
• App ID and App Secret (AGOL/Portal application)
• Portal URL (for federated Enterprise)
• A Viewer user (username/password) or equivalent read access

Before You Enable Sync — Data Prerequisites

1. Each published layer must reference its own feature class in the geodatabase (no group layers, no joins relating multiple classes into one layer).
2. All feature classes require GlobalIDs (run Add Global IDs in ArcGIS Pro if missing).
3. Pick one change-tracking model:
   • Traditional versioning + Archiving, or
   • Non-versioned editing with Archiving, or
   • Branch versioning with appropriate change tracking (Enterprise).
4. Attachments enabled where needed (photos, files).
5. Remove unsupported layer types (e.g., certain views, dynamic joins, or non-editable tables) from the feature service.

In ArcGIS Pro — Prepare & Publish

The following steps are provided as general guidance. Please reach out to your organization’s GIS/IT team is for administering ArcGIS; while ITpipes can help confirm requirements and provide support, we cannot directly configure ESRI environments.

Prepare the Data

1. Add the feature classes (e.g., Mains, Manholes, Laterals) to a single map in your Pro project.
2. Run Add Global IDs on each class.
3. Enable Attachments where required.
4. Configure Archiving and/or Versioning per your workflow.

Publish the Feature Service

1. In Pro: Share → Web Layer → Feature (choose your Portal/AGOL target).
2. On the sharing pane:
   • Set Capabilities: enable Editing (as needed) and Sync (required for offline/replica).
   • Verify each map layer points to a distinct feature class.
   • Analyze → resolve any errors/warnings, then Publish.

Example layer mapping:

• Layer 0 — Sewer_Mains (line feature class)
• Layer 1 — Manholes (point feature class)
• Layer 2 — Laterals (line feature class)

In ArcGIS Online (AGOL) — Hosted Feature Layer

1. Open the Item page for the Hosted Feature Layer.
2. Go to Settings and enable Sync (required for offline use).
3. Under Sharing, set visibility and groups to meet ITpipes access needs.
4. Register an Application (Content → Add Item → Application) to obtain App ID and Secret. Add the ITpipes callback to your Redirect URL list if requested.

In ArcGIS Enterprise — Feature Service on ArcGIS Server

1. Publish from ArcGIS Pro to your federated portal as a Feature web layer, or publish to ArcGIS Server with Feature Access enabled.
2. In ArcGIS Server Manager:
   • Open the service → Capabilities and check Feature Access and Sync.
   • Save and restart the service.
3. Ensure the data store is properly registered and that GlobalIDs/archiving/versioning are configured on the source geodatabase classes.

Verify Sync & Create Replica

ITpipes can assist with the Replica Creation process to confirm what is needed o return a successful outcome. 

1. Open the REST endpoint for your feature service (.../FeatureServer?f=pjson or layer index).
2. Confirm "capabilities" includes Sync.
3. On the service (or layer) REST page, look for Operations and verify createReplica is listed. The UI will show a Create Replica form when Sync is enabled.

App Registration / Credentials

1. In AGOL/Portal, create an Application item to obtain App ID and Secret.
2. If using Enterprise SSO (e.g., Entra/Okta), also provide the Portal URL.
3. Provide ITpipes with a Viewer user (or equivalent) for validation.
4. Add the ITpipes URL to your organization’s Redirect URL list if requested.

Troubleshooting

Error: “XML Parser initialization failed. Edit operation will be reverted.”

This occurs when the server can’t apply the Sync capability to the service configuration. Common fixes:

1. Confirm the service is a Feature Service (not just a Map Service).
2. Ensure GlobalIDs exist on all feature classes.
3. Configure Archiving and Versioning model correctly (traditional+archiving, non-versioned+archiving, or branch+change tracking).
4. Remove unsupported layers/joins and republish from ArcGIS Pro with Sync checked at publish time (preferred over toggling post-publish).
5. Restart the service in Server Manager, then re-check capabilities.

“Create Replica” not visible on REST page

• We could be viewing /MapServer instead of /FeatureServer.
• Sync is not in the service capabilities.
• Your account lacks privileges to use replica operations; test with the service owner/admin.

Integrating with ITpipes

Once your feature service is sync-enabled, please share the Feature Service URL, App ID, and Secret with ITpipes. For federated environments, also provide the Portal URL and ensure the CoreVision web URL is in your Redirect URL list. ITpipes will configure and download the map in CoreVision allowing us to leverage the Replica for any ITpipes Mobile units

Quick Checklist

• Feature Service Selected
• GlobalIDs on all feature classes
• Archiving / Versioning model set
• Sync enabled at publish (or in item settings for hosted)
• “createReplica” visible on REST page