Navigation:  Step-By-Step Importing > Mapping Input Fields

Mapping import fields is done via "drag 'n drop" regardless of the import mode being used. The only difference is mapping function is when the Import mode is either <Update> or <Delete>, in which case, key fields must be identified matching one or more Outlook fields to corresponding fields in the input data file.

 

In all cases, a field is selected from the Field Tree and moved to the appropriate corresponding input data file field in the <To Column>.

 

If the field is dropped on the wrong location, it can simply also be moved via a drag and drop from one field to another. The same Outlook field cannot be mapped to multiple <To Fields>.

 

A field can be removed from the <To Field> list by clicking on it once.

 

 

<ADD Only -Allow Dupes> Import Mapping screen

 

 

 

Add / Delete / Update Import Mapping screen

 

A checkbox will automatically appear when the import mode is either <Add - Ignore/Replace Dupes>, <Update> or <Delete> and at least one field must be selected in order to be able to process the import. Only the fields required to match contacts in the destination folder to records in the input data source should be checked.

 

 

 

User-defined fields

 

If the current selected Message Class is the standard form (IPM.Contact), then all fields in the "User-defined fields in folder> will be displayed (if any). Otherwise, the custom fields assigned to the custom form will be displayed. It will be one or the other - never both - see Outlook Fields

 

Auto-Mapping

 

When the input data source is selected, CDP performs a scan of the input file field list against the Outlook fields  (both standard and user-defined). If a match is found on either the Outlook internal field or the current Outlook DisplayAs field name (regardless of which setting is actually in force in terms of <Show Fields As>) - the field will be <auto-mapped>.

 

All auto-mapped fields should be reviewed for accuracy since it is possible for a field name in the input data file to match an Outlook field but not be correct. One field name that could easily be mapped in correctly would be one named <City> which would auto-map to the <MailingAddressCity> field when in fact it be pertain to another address group (Home, Business, Other).

 

 

Dynamic User-Defined Field Assignment/Creation

 

This option will only be available/visible when the currently selected message class is <IPM.Contact> - the standard Outlook messageclass / form. For more information see Adding User-defined fields