Conflict policy

When a conflict is detected on either the source or the destination, Conflict Policy determines how DataHub will behave

Keep both files

Conflict Copy: When a file changes on both the Source and the Destination, Conflict Copy will identify the versions for the file and append a time-stamp to preserve the integrity of each. We will make a copy of the earliest version then override the content with the latest. (default)

Extended Description: Conflict Copy is the system default for Conflict Policy. Based on your transfer type selected, you can expected the following behavior for Conflict Copy Policy:

Synchronize - Will always prefer the latest version and put the Conflict Copy on the side that is the earliest

Copy - Will always prefer the version located on the Source and put the conflict copy on the Destination

Migrate - Conflict Copy Policy is not applicable. With transfer type Migrate, the application will always prefer the Source. Also, since the application does not run change detection on subsequent job runs for Migrate, conflict policy would not be applicable

Publish - Conflict Copy Policy is not applicable. With transfer type Publish, the application will always prefer the Source; regardless of conflict

Move - Conflict Copy Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, conflict policy would not be applicable

Copy Folder Structure - Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, conflict policy would not be applicable

Prefer most recently modified file

Prefer Latest: When a file changes on both the Source and the Destination, Prefer Latest will identify the versions for the file and override the content with the latest.

Extended Description: Based on your transfer type selected, you can expected the following behavior for Prefer Latest Policy:

Synchronize - If the latest version is on the Source, the application will transfer from the Source and override the Destination with the latest version. If the latest version is on the Destination, the application will transfer from the Destination and override the Source with the latest version

Copy - If the latest version is on the Source, the application will transfer from the Source and override the Destination with the latest version. If the latest version is on the Destination, the application will skip the file for transfer and flag with a "Not Allowed" failure in the log.

Migrate - Prefer Latest Conflict Policy is not applicable. With transfer type Migrate, the application will always prefer the Source. Also, since the application does not run change detection on subsequent job runs for Migrate, Prefer Latest Conflict Policy would not be applicable

Publish - Prefer Latest Conflict Policy is not applicable. With transfer type Publish, the application will always prefer the Source; regardless of conflict

Move - Prefer Latest Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, Prefer Latest Conflict Policy would not be applicable

Copy Folder Structure - Prefer Latest Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Latest Conflict Policy would not be applicable

Prefer the version on source

Prefer Source: When a file changes on both the Source and the Destination, the Destination will always be overridden; regardless of version.

Extended Description: Based on your transfer type selected, you can expected the following behavior for Prefer Source Policy:

Synchronize - Will always transfer from the Source and override on the Destination; regardless of which version is later

Copy - Will always transfer from the Source and override on the Destination; regardless of which version is later

Migrate: Prefer Source Conflict Policy is not applicable. With transfer type Migrate, the application will always prefer the Source. Also, since the application does not run change detection on subsequent job runs for Migrate, Prefer Source Conflict Policy would not be applicable

Publish - Prefer Source Conflict Policy is not applicable. With transfer type Publish the application will always prefer the Source; regardless of conflict

Move - Prefer Source Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, Prefer Source Conflict Policy would not be applicable

Copy Folder Structure - Prefer Source Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Source Conflict Policy would not be applicable

Prefer the version on destination

Prefer Destination: When a file changes on both the Source and the Destination, the Source will always be overridden; regardless of version.

Extended Description: Based on your transfer type selected, you can expected the following behavior for Prefer Destination Policy:

Synchronize - Will always transfer from the Destination and override on the Source; regardless of which version is later

Copy - Will always transfer from the Destination and override on the Source; regardless of which version is later

Migrate: Prefer Destination Conflict Policy is not applicable. With transfer type Migrate, the application will always prefer the Source. Also, since the application does not run change detection on subsequent job runs for Migrate, Prefer Destination Conflict Policy would not be applicable

Publish - Prefer Destination Conflict Policy is not applicable. With transfer type Publish, the application will always prefer the Source; regardless of conflict

Move - Prefer Destination Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, Prefer Destination Conflict Policy would not be applicable

Copy Folder Structure - Prefer Destination Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Prefer Destination Conflict Policy would not be applicable

Flag the file

Failure: When a file changes on both the Source and the Destination, Failure will flag the file and log it. The conflict file will be skipped and no changes will occur.

Extended Description: Based on your transfer type selected, you can expected the following behavior for Failure Policy:

Synchronize - If the application detects a conflict, it will be flagged and logged as failure. The conflict file will be skipped and no changes will occur

Copy - If the application detects a conflict, it will be flagged and logged as failure. The conflict file will be skipped and no changes will occur

Migrate: Failure Conflict Policy is not applicable. With transfer type Migrate, the application will always prefer the Source. Also, since the application does not run change detection on subsequent job runs for Migrate, Failure Conflict Policy would not be applicable

Publish - Failure Conflict Policy is not applicable. With transfer type Publish, the application will always prefer the Source; regardless of conflict

Move - Failure Conflict Policy is not applicable. With transfer type Move, the application will always prefer the latest version. Also, since the application does not run change detection on subsequent job runs with Move, Failure Conflict Policy would not be applicable

Copy Folder Structure - Failure Conflict Copy Policy is not applicable. Since there are no conflicts when copying folders, Failure Conflict Policy would not be applicable

Example JSON

Configuration options include:

copy (default)
latest
source
destination
failure

POST {{url}}v1/jobs

{
  "name":"Conflict Policy Test",
  "kind": "transfer",
  "transfer": {
      "audit_level": "trace",
      "transfer_type": "copy",
      "conflict_resolution": "latest",
      "source": {
        "connection": { "id": "{{cloud_connection_source}}" },
        "target":
        {"path":"/SourcePath"}
      },
      "destination": {
        "connection": { "id": "{{cloud_connection_destination}}" },
        "target": {
          "path": "/DestinationPath"
        }
      }
  },
  "schedule": {
    "mode": "manual"
  }
}

Syncplicity Support

iPad

iPhone

Android

Windows

Mac

Outlook Add-in for Windows

My Syncplicity

Outlook Add-in for Office 365

Known issues

Salesforce for users

Account Management

Reports

Policies

Clients

Users and Groups

Storage Vaults

Connectors

Syncplicity Rights Management

DataHub v4

Syncplicity for Salesforce

Events Tracking

Release Notes for Administrators

New to Syncplicity