Understanding Intellisync for SalesLogix Field Mapping

Intellisync for SalesLogix works by moving data between connectors (or sometimes a connector and translator) and does not directly connect one database to another. For example, when you export data from Sage SalesLogix to Microsoft Outlook or Lotus Notes, Intellisync uses both the Sage SalesLogix and the Outlook or Lotus Notes connectors. The Sage SalesLogix connector reads the data in the Ad Hoc group you specified during configuration; the Outlook or Lotus Notes connector reads the data in the SyncSalesLogix category in Outlook or Lotus Notes.

During a manual synchronization, Intellisync compares the data in both connectors and presents you with confirmation screens where you can look at the changes and either accept or reject them. During an automatic synchronization, the process is the same however, there are no confirmation screens. Intellisync relies on the configuration settings to resolve any conflicts.

Synchronization only transfers data between fields that are mapped; unmapped fields are ignored. A standard set of mapped fields is provided with Intellisync for SalesLogix. Tables detailing the default field maps are available in the Sage SalesLogix Administrator Help. You can view and redefine current field maps, map additional fields, or remove field maps to meet your business requirements. Field maps are specific to the translator or connector version installed and the type of action requested.

Creating a new map between previously unmapped fields enables synchronization of the data between applications. Removing a map ends synchronization of the data previously mapped. For information about changing how data is mapped, see the help topics available through the Intellisync for SalesLogix Application Setup Wizard.

It is important to remember that changing field maps can produce unexpected results. Therefore, before customizing mapped fields, be sure to back up your data before synchronizing. It is also advisable to create test files to see how your changes affect critical data.
If you change mapped fields for data that has already been synchronized, the next synchronization that occurs is, in effect, a first synchronization run. For this reason, you should run Intellisync for SalesLogix synchronization before making changes to mapped fields.