When two separate applications are connected, there is the possibility that related entities can each be updated simultaneously, creating a conflict. It is important to know when this happens and how it is resolved. When a conflict occurs, it is logged and an email is sent to the configured users in the Notifications section that are stored in the Entity Mapping tab of each automation. If there is no contact information specified in the Entity Mapping tab, the email(s) will be sent to the user(s) configured in the Email Configurations page.
In the Configuration tab, there is a Conflict Management Strategy drop-down box with 4 options:
| Option | Result |
|---|
| Fixed | The application that you select as Fixed takes precedence in case of conflict and the values from the Fixed application will always overwrite the other. |
| First In | When you select First In, the change made by the application that writes first will be considered during synchronization (if there is a conflict), and the submission of the second application will be discarded. |
| Last In | When you select Last In, the change made by the application that writes last will be considered during synchronization (if there is a conflict), and the submission of the first application will be overwritten. |
| None | No conflict management logic will be used. This strategy is intended for use in unidirectional automations and unidirectional field mappings where a conflict-management strategy is not needed. Note that setting the strategy to None disables the internal processing and caching of the field values. If you do use None in a bidirectional automation, however, the field values will be swapped in the event of a conflict (a mapped field changing on both sides of the automation in the same poll interval). |
You can also set a conflict management strategy based on specific fields. To learn more, see Field Level Conflict Management.