Sync Conflicts
Package: BASIC
1. General
The Sync Conflicts module lists all records where synchronization problems have occurred due to missing values in required fields.
Synchronization problems can occur in connection with the following functions:
There are no configuration options for the Sync Conflicts module in Module Management.
An automation tries to create a new record but fails because a required field is not populated. The record appears in the Sync Conflicts module with the Conflict Source Automation. Via the Resolve Conflict action, the record is opened in the edit view, the missing required field is added and the conflict is thus resolved.
After an Exchange Online synchronization, multiple records with conflicts are present. Via Bulk Resolve, all affected records are marked via checkbox and the edit view opens for each record in succession, so that the missing values can be quickly added.
2. List View
In the list view, the affected records are displayed including a note on the conflict source. From the list view, the respective records can be called up directly and the conflicts resolved.
The list view contains the following columns:
- Conflict No.
- Created
- Target Module
- Conflict Source
- Additional Information
- Responsible
- Action
2.1. Actions
In the list view, general actions are available depending on the module. An overview and description of all general actions can be found in the section Actions (List View).
The following module-specific actions are also available:
| Action | Prerequisite | Functionality |
|---|---|---|
| Resolve Conflict | none | Opens the affected record in the edit view of the respective module; the missing required fields can be added there and the conflict resolved |
| Bulk Resolve | none | Enables the simultaneous editing of multiple records; the desired records are selected via checkbox, the edit view then opens for each record in succession |
The Resolve Conflict action is available for each record individually in the Action column. After clicking, the affected record opens in the edit view of the respective module, where the missing required fields can be added and the conflict resolved.
3. Detail View
A detail view of records within this module is not available.
4. Practical Examples
1 – Resolving a Single Sync Conflict from an Automation
An automation tries to automatically create a contact record when a new email arrives. Since a configured required field – e.g., the last name – cannot be determined from the email, the creation fails. The record appears in the Sync Conflicts module with the Conflict Source Automation and a corresponding note in the Additional Information column.
The responsible employee opens the entry and clicks Resolve Conflict in the Action column. The affected record opens in the edit view of the Contacts module. The missing required field is added and the record is saved. The sync conflict is thus resolved and disappears from the list.
2 – Resolving Multiple Conflicts After an Exchange Online Synchronization
After an Exchange Online synchronization, several contact records with conflicts have appeared in the list because required fields in brainX could not be populated with the synchronized Exchange data. To resolve the conflicts efficiently, all affected records in the list view are marked via checkbox.
Via the Bulk Resolve action, the edit view opens for each record in succession. The missing required fields are added and saved one after another. After completion, all conflicts are resolved and the list is empty again.
3 – Regularly Monitoring and Prioritizing Sync Conflicts
An administrator wants to ensure that sync conflicts are resolved promptly and don't accumulate unnoticed. For this purpose, a filtered view by Conflict Source is set up in the list view of the Sync Conflicts module – e.g., to separate conflicts from automations from those from Exchange synchronization.
The conflicts are processed by priority: First, conflicts from critical automations are resolved, as these can have direct effects on running processes. Subsequently, Exchange conflicts are efficiently processed via bulk resolution. Regular monitoring of the module ensures that no records remain permanently incomplete in the system.
5. Frequently Asked Questions
What are sync conflicts and how do they arise?
Sync conflicts arise when a synchronization process – e.g., from an automation, the Exchange Online integration or time tracking – tries to create or update a record but a required field cannot be populated. The affected record is listed in the Sync Conflicts module until the missing value is manually added.
How do I resolve a sync conflict?
In the list view of the Sync Conflicts module, the Resolve Conflict action is available in the Action column. After clicking, the affected record opens in the edit view of the respective module. The missing required field is added there and the record is saved – the conflict is thus resolved.
Can I resolve multiple conflicts simultaneously?
Yes. Via the Bulk Resolve action, multiple records can be selected via checkbox. The edit view then opens for each affected record in succession, so that the missing values can be efficiently added one after another.
Which sources can cause sync conflicts?
Sync conflicts can arise from three sources: the Exchange Online integration, automations and time tracking. The respective source is visible in the Conflict Source column of the list view.
Is there a detail view for individual sync conflicts?
No. The Sync Conflicts module has no detail view for individual records. All relevant information – conflict number, target module, source and additional information – is viewable directly in the list view.
Can the Sync Conflicts module be configured in module management?
No. There are no configuration options for the Sync Conflicts module in module management – neither for custom fields nor for layouts or permissions.