Information about the capabilities supported by a sync-enabled service. More...
|Import Statement:||import Esri.ArcGISRuntime 100.10|
- supportsAsync : bool
- supportsAttachmentsSyncDirection : bool
- supportsRegisteringExistingData : bool
- supportsRollbackOnFailure : bool
- supportsSyncDirectionControl : bool
- supportsSyncModelGeodatabase : bool
- supportsSyncModelLayer : bool
- supportsSyncModelNone : bool
Note: You cannot declare or create a component of this type in QML code.
Returns whether the service supports asynchronous operations. This avoids server timeouts (read-only).
Returns whether the service supports options to define how attachments will be synced. (read-only).
Returns whether the service supports registering an existing mobile geodatabase (*.geodatabase file) as new a sync-enabled geodatabase (read-only).
This is useful when you already have a geodatabase that you want to sync on multiple devices independently without affecting each other.
Returns whether the service supports rolling back edits in case of a failure during sync operations (read-only).
Returns whether the service allows the client application to control direction of sync (read-only).
This directions include upload only, download only, or bi-directional.
Returns whether the service supports sync capabilities for the entire sync-enabled geodatabase (read-only).
All layers in the geodatabase will be synchronized together in the same direction.
Returns whether the service supports sync capabilities independently on a layer-by-layer basis in the sync-enabled geodatabase (read-only).
For example, one layer can upload changes while another downloads during sync. A perLayer sync model also allows clients to limit the sync to a subset of layers in the geodatabase.