Managing Legacy Conflict Issues¶

The following describes a process for managing data conflicts using a deprecated feature known as "Auto-merge" and "Conflict Issues".

When using Sync Protocol 2 we can sync data down to Devices. Because of this it is possible for two Devices to edit the same data between syncs. This causes a "Data Conflict". When a Device is syncing and a conflict is detected, the Tangerine software will try to resolve that conflict by merging the two versions. When Tangerine does this, it creates a "Conflict Issue" which stores the two versions and the merged version for safe keeping (in Issue this is refered to as A, B, and Merged). These are important to review in the Issue queue to ensure that the merge is satisfactory. Sometimes a merge will not be possible and the data will be left in a Conflict state according to CouchDB's definition of Conflict.

To manage Data Conflicts you will need to know the IP Address of your server and CouchDB Admin credentials found in config.sh.

Monitor how many Conflict Issues there are by Document ID¶

1. Go to <serverIpAddress>:5984/_utils/#/database/<groupId>/_design/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId/_view/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId
2. Click wrench for view on left hand column, make sure "Reduce: Count" is enabled on the view.
3. Click "Options", check "Reduce" and then set "Group Level" of 2.

Get a list of all conflict issues in a group¶

<serverIpAddress>/<groupId>/_design/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId/_view/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId?reduce=false

Check a single document for conflicts¶

Get a list of all conflict issues for a document¶

If you know the document id for a case, you can get a list of its conflict issues.

In the following example, the first parameter in the key is set to 'case' to signify that it is a case document (type:'case'); however, in the future conflicts may also betype:'response'.

Replace <docId> and enter the following into your browser:

<serverIpAddress>/<groupId>/_design/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId/_view/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId?reduce=false&key=["case","<docId>"]

Get the number of conflicts in a document¶

If you know the document id for a case, replace <docId> and enter the following into your browser:

<serverIpAddress>/<groupId>/_design/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId/_view/issuesOfTypeConflictByConflictingDocTypeAndConflictingDocId?reduce=true&group_level=2&key=["case","<docId>"]

Monitor active Database Conflicts in CouchDB¶

Go to <serverIpAddress>:5984/_utils/#database/<groupId>/_design/shared_conflicts/_view/shared_conflicts.

To view the number of conflicts per document, click the table tab.

To resolve a conflict, click on the row to open the Doc in conflict. Then click the "Conflicts" tab to resolve the Conflict.

Viewing the history of Documents in the database¶

Sometimes it helps to look back at the history of a Case. When a Case is open in Tangerine Editor, you can run the following in the Chrome Devtools Console.

await T.case.getCaseHistory()

To look at the full picture that CouchDB server is aware of, use the following URL structure...

<serverIpAddress>:5984/<groupId>/<docId>?revs_info=true

<serverIpAddress>:5984/<groupId>/<docId>?rev=<revId>