Step-By-Step Importing > Import statistics

Once the import preview or actual import process starts, the <Import/Export> statistic screen will be displayed showing the import progress.

ImpStats

Notes:

#Added

The number of contacts updated reflects the total number of contacts records added during the import process.

#Updated

The number of contacts updated reflects the total number of contacts records found that match the input data records where at least one field in the contact item had a different value then that found in the input data source. In this test scenario, the contact folder contained 5 duplicate records for each contact.

#Failures

This number represents contact items that could not be updated. The most common reason for this to occur is validation criteria that exists for the contact item on any field and the data being imported fails the validation rules. There is no way to programmatically bypass any existing validation rules so if the requirement is that all contacts are imported - then no validation rules should be set.

#Deleted

The number of contacts updated reflects the total number of contacts records deleted during the import process. Contacts can only be deleted via the <Delete Matched> Import Mode.

#No Changes

Reflects the number of contact items where all the fields for a given contact item contained identical field values in the input data record that matched the contact item based on the <Update Key> field selected. Starting with MultiPort v1.2, contact items are no longer updated if no differences were found in any fields resulting in the LastModificationDate remaining unchanged

#Bypassed

This value represents the number of contacts that could not be read for whatever reason and as a result bypassed for processing. Generally this could occur if a specific contact item is corrupt. A very large number would indicate some kind of underlying problem which should be investigated.

#No Unqiue Dupes (Source)

This only applies to an <Update> import and represents the number of unique records that have the same value for the <Update Key Fields> specified in the source data file where items are being imported <FROM> (Source).

For example, for the sake of simplicity, assuming that the <Email1Address> field is designated as the only <Update Key Field> (used to match records in the input file being imported to Outlook contact items) and the input data file contained records with the following email addresses:

Rec#1: <abc@def.com>

Rec#2: <abc@def.com>

Rec#3: <def@ccc.com>

Rec#4: <xyz@gfh.com>

Rec#5: <xyz@gfh.com>

The number of Unique Dupes would equal <2> - one for (Recs 1&2) and one for (Recs 4&5)

#No Total Dupes (Source)

Using the same example of existing input data records as described in <#No Unique Dupes (Source) - the total number of Dupes would be equal to <4> - two for (Recs 1&2) and two for (Recs 4&5)

The significance of having duplicate records in an input data file is that each record found in the input data file will update the Outlook contact item if differences are found in any of the fields. In short, the values found in the last of the duplicate records processed will be reflected in the Outlook contact items that are found to match the <Update Key> fields.

#No Unqiue Dupes (Dest)

This only applies to an <Update> import and represents the number of unique records that have the same value for the <Update Key Fields> specified in the Outlook folder where items are being imported <TO> (Destination).

For example, for the sake of simplicity, assuming that the <Email1Address> field is designated as the only <Update Key Field> (used to match records in the input file being imported to Outlook contact items) and the Outlook contact folder contained records with the following email addresses: