Resolving Conflicts

Conflicts are resolved at the record level. The following table lists the core fields used to determine conflict resolution:

Address Book/Contacts	To-Do's	Appointment/Scheduled
First Name	Description/Subject	Date/Start Date
Last Name	Contact Name	Description/Subject
Middle Name	Contact Company
Company	Contact Phone

Key fields are case-sensitive, so if you have a record for Lee Hogan in Sage SalesLogix and one for lee hogan in Microsoft Outlook or Lotus Notes, the records are not equal. Both records are added to each system during synchronization.

Conflict resolution settings are configured in the Intellisync for Sage SalesLogix Application Setup. These settings enable you to control conflicts between SalesLogix and Microsoft Outlook or Lotus Notes. You can mark a particular application as the source for automatic conflict resolution, or you can choose to be notified when a conflict occurs. Notification allows you to compare the fields in question, and then make your own decision regarding the data. For example, if a contact has a different account phone number in Sage SalesLogix than in Microsoft Outlook or Lotus Notes, you are asked to resolve the conflict by selecting the phone number you want to use. You can also configure Intellisync for SalesLogix to add or ignore all conflicting items, although this method is not recommended.

If you choose to be prompted when a conflict occurs, you can see a summary of proposed changes before the data transfer occurs. You can establish these options when you configure Intellisync for SalesLogix. After reviewing the information, you can confirm that you want to proceed.

Conflict Resolution Notes

The following notes are helpful tips for conflict resolution:

In addition to key fields, Intellisync for SalesLogix sometimes uses unique identifiers to determine how changes are applied to records during synchronization. These identifiers cannot be viewed, but allow the program to detect changes made to key fields.
The conflict resolution setting is not normally needed to resolve conflicts between records. In most cases, the program automatically edits records to achieve synchronization.
Overlapping appointments are not treated as data conflicts.
Last Name fields in address records cannot be left blank. Since Last Name fields are key fields, a blank field can generate false data conflicts.
If there is no name to enter in an address record — for example, if you have an address for a company, but you do not have a contact name — place another value in the Last Name field, such as the company name. If you have only a contact’s first name, enter the first name in both the Last Name and the First Name fields.
The “Notify me when conflicts occur” (default setting) is the only conflict resolution setting that allows you to view each data conflict and decide how the conflict should be resolved. All other conflict resolution settings work without user action.