Esri ArcGIS Sync Overview

CivicPlus Asset Management provides seamless synchronization with your Esri GIS environment, ensuring consistent, up-to-date asset data across both platforms. Whether using ArcGIS Online or ArcGIS Enterprise, our Logic App–based integration automates data flow, minimizes manual updates, and maintains a single authoritative source of truth for all asset information.

The integration supports both secured and anonymous (publicly accessible) Esri feature services. Token-based authentication is used where required to support secured access, auditing, and advanced synchronization capabilities.

The CivicPlus Asset Management GIS Sync integration provides flexible synchronization options for organizations at all stages of GIS maturity, from read-only data alignment to fully bi-directional data exchange. Our implementation approach ensures security, accuracy, and reliability while adapting to your organization’s preferred Esri environment and governance model.

Integration Overview

The GIS Sync Integration enables secure, automated data exchange between CivicPlus Asset Management and Esri REST (Representational State Transfer) endpoints, operating at the feature service layer level within ArcGIS Online or ArcGIS Enterprise environments. This ensures compatibility across hosted, registered, and versioned datasets without requiring direct database connections.

Key Benefits

• Automated synchronization of GIS and asset data

• Data integrity safeguards through validation of feature identifiers, domain values, and lookup alignments during synchronization to ensure accurate representation of GIS attributes within Asset Management.

• Supports both secured and anonymous Esri feature services for GIS to Asset Management synchronization, where supported.

• Secure token-based authentication for secured services and all advanced workflows, including deletion tracking and bi-directional synchronization.

• Configurable one-way or bi-directional data exchange based on operational requirements.

• Streamlined onboarding for AGOL or Enterprise environments.

Supported Synchronization Models

Each synchronization model can be configured at the layer level within the integration environment, allowing different asset classes, such as valves, hydrants, or mains, to participate in distinct sync workflows based on operational needs.

Access Model Summary

This section summarizes the supported access and authentication models for the CivicPlus Asset Management GIS Sync Integration. The appropriate model depends on the Esri feature service configuration and the desired synchronization capabilities.

Overview

The GIS Sync Integration operates against Esri REST (Representational State Transfer) feature services and supports both anonymous (public) and secured access models. Authentication requirements vary based on whether the integration performs read-only queries or advanced synchronization operations such as deletion tracking or bi-directional updates.

Support Access Models

Anonymous Read-Only Access (GIS to Asset Management)

Uses publicly accessible Esri feature services to perform read-only synchronization from GIS into Asset Management using standard query operations.

Authentication

• No token required

• No integration user required

• No token URL,username, or password configured

Support Capabilities

• Initial data load

• Attribute updates from GIS to Asset Management

• Geometry ingestion

• Scheduled synchronization

Limitations

• Deletions in GIS are not detected

• Bi-directional updates are not supported

• ExtractChanges and ApplyEdits are not used

Typical Use Case

• Organizations exposing public-facing GIS layers

• Read-only asset synchronization

• Lightweight integrations with minimal administrative overhead

Secured Read-Only Access (GIS to Asset Management)

Uses secured Esri feature services with token-based authentication to perform read-only synchronization via query.

Authentication

• Token-based authentication required

• Integration user account required

• Token generation URL configured

Support Capabilities

• Initial data load

• Attribute and geometry updates from GIS to Asset Management

• Scheduled synchronization

Limitations

• Deletions in GIS are not detected

• Bi-directional updates are not supported

Typical Use Case

• Internal or restricted GIS environments

• Organizations requiring authenticated access even for read-only data

Secured Access with Deletion Tracking (GIS to Asset Management)

Uses secured feature services with ChangeTracking (ExtractChanges) enabled to detect inserts, updates, and deletions in GIS.

Authentication

• Token-based authentication required

• Integration user with Sync or Edit privileges required

Supported Capabilities

• Incremental updates using serverGen values

• Detection and processing of deletions

• Attribute and geometry updates

Limitations

• Anonymous access is not supported

• Bi-directional updates require additional permissions

Typical Use Case

• GIS environments where deletions must be reflected in Asset Management

• Enterprise or AGOL (ArcGIS Online) hosted services with change tracking enabled

Secured Bi-Directional Synchronization

Enables full two-way synchronization between Asset Management and GIS using ApplyEdits and ExtractChanges.

Authorization

• Token-based authentication required

• Dedicated integration user with Create, Update, and Delete permissions

Supported Capabilities

• Feature creation, updates, and deletions in both systems

• Editor tracking and auditability

• Full lifecycle asset management

Limitation

• Anonymous access is not supported

• Requires careful schema and domain alignment

Typical Use Case

• Shared data stewardship between GIS staff and field or operational users

• Enterprise environments with mature governance models

Access Model Comparison Summary

Key Notes

• Anonymous access is supported only for read-only GIS to Asset Management synchronization.

• Deletion tracking and bi-directional workflows always require secured feature services and token-authenticated access.

• The integration does not require changes to existing Esri sharing models; access requirements are driven by desired functionality.

• CivicPlus recommends engaging GIS administrators early to select the access model that best aligns with operational and security needs.

Technical Requirements

Important Note:

Token-authenticated access is required for secured feature services and all advanced

workflows (deletion tracking and bi-directional synchronization). Anonymous feature services

are supported for read-only GIS to Asset Management synchronization.

Technical requirements vary by access model. Refer to the Access Model Summary to identify the applicable requirements for your environment.

GIS to Asset Management (No Deletion Tracking)

• Required Attributes: GlobalID, EditedDate (or equivalent)

• Service Capabilities: Query, Advanced Queries

• Query Formats: JSON, GeoJSON

• Permissions: Read access for integration user

• Anonymous access is supported for this model when feature services are publicly accessible

GIS to Asset Management (With Deletion Tracking)

Deletion tracking requires token-authenticated access and is not supported for anonymous feature services.

• Required Attributes: GlobalID

• Service Capabilities: ChangeTracking enabled

• Required Properties:

  • supportsReturnIdsOnly: true

  • supportsServerGens: true

  • supportsLayerQueries: true

  • supportsAdvancedQueries: true

  • isDataVersioned: true

• Query Formats: JSON, GeoJSON

• Permissions:

  • Sync-enabled or Edit (Add/Update/Delete) access is required for the integration user to execute the ExtractChanges operation and retrieve deletions from the layer’s delta tables. The integration polls the serverGen value to identify and retrieve new or deleted features. Deletions are transmitted as GlobalID references rather than feature geometries.

  • Depending on the Esri environment, deletion tracking may require elevated privileges.

    • ArcGIS Enterprise ChangeTracking typically requires users with sync or edit privileges.

    • Read-only users can consume AGOL Sync-based change tracking if the layer is shared accordingly.

Bi-directional Synchronization

• Required Attributes: GlobalID

• Service Capabilities: ChangeTracking and ApplyEdits

• ApplyEdits Options:

  • useGlobalIDs: true

  • trueCurveClient: true

  • Changes made in Asset Management are posted back to the GIS feature service using the ApplyEdits operation and are tracked under the integration user’s editor credentials.

• Permissions: Create, Update, and Delete access for integration user

  • Because ApplyEdits operations modify feature data, bi-directional synchronization always requires a secured feature service and a dedicated integration user.

Environment Compatibility

Important Note:

Anonymous feature services are supported only for environments using standard query-based synchronization without deletion tracking.

Information Needed from Your Team

Important Note:

An integration user and token URL are required only for secured feature services or workflows involving deletion tracking or bi-directional synchronization. Anonymous, read-only integrations do not require credential configuration.

To configure your integration, we will need:

• Preferred sync type, such as one-way or bi-directional

• Integration username and password

• Token generation URL: https://www.arcgis.com/sharing/generateToken

• URLs of the hosted or registered feature services to integrate

• Confirmation of ChangeTracking or Sync status

• Confirmation of feature service ownership

  • Hosted vs. Registered

• Contact for GIS Administrator or GIS Coordinator for validation of service settings

Publishing and Configuration Guidance (ArcGIS Enterprise)

The following requirements apply to secured feature services participating in deletion tracking or bi-directional synchronization. If your organization uses ArcGIS Enterprise, ensure the following steps are completed before integration:

1. Enable Branch Versioning: Recommended for Enterprise 10.9+; allows full conflict and edit history management.

2. Enable Editor Tracking: Include CreatedBy/CreatedDate and EditedBy/EditedDate fields.

3. Enable ChangeTracking (ExtractChanges): Required for deletion tracking and incremental sync.

   1. Ensure all editor tracking fields are mapped in the layer properties and included in the outFields list, such as created_user, created_date, last_edited_user, or last_edited_date. These fields improve the traceability of integration-driven updates.

4. Publish as a Feature Service: Include capabilities: Query, Create, Update, Delete, ChangeTracking, and Version Management.

   1. If multiple feature classes share relationships, such as parent-child asset layers, publish them within the same service definition to preserve relationship integrity during synchronization.

5. Verify Service Endpoints: Confirm ApplyEdits and ExtractChanges endpoints respond successfully via Portal or ArcGIS Pro.

Glossary

• ChangeTracking (ExtractChanges): Esri capability that tracks inserts, updates, and deletions in a feature service.

  Note:

  Required for deletion synchronization.

• serverGen: Numeric generation identifier Esri uses to track incremental data changes since the last sync.

• ApplyEdits: REST (Representational State Transfer) endpoint used to create, update, or delete features within a layer.

  Note:

  Required for bi-directional synchronization.

• Branch Versioning: ArcGIS Enterprise data management model supporting concurrent editing and conflict resolution.

• AGOL Hosted Feature Service: A feature service stored natively in ArcGIS Online rather than a local geodatabase.