Why can't I import duplicate records although I'm using custom duplicate criteria?

Environment:

Data Import Wizard
Oracle B2C Service

All versions

Resolution:

If you are trying to import duplicate records by using a custom duplicate criteria, note that the Oracle B2C Service application already has in place a set of default criteria which take precedence over the custom ones.

The following fields are automatically included as default duplicate criteria whenever they are included in the mapping grid:

• Email Address - When importing contacts, to simplify detection of redundant values in the primary and secondary email address fields (email, email_alt1, and email_alt2), the expression references them together as any_email. For example, any_email={1}.

• Contact ID, Organization ID, Incident ID, Answer ID - These fields are included as default criteria when importing their primary record type. Because these fields are unique for every record, additional criteria would not be more restrictive. For this reason, OR logic is used whenever they are added to the duplicate criteria. For example, any_email={1} OR c_id={2}.

• First and Last Name - If email address sharing is enabled, first_name and last_name is included when importing contacts. This narrows the criteria by permitting multiple contacts that share a common email address as long as they have different first or last names. For example, any_email={1} AND first_name={2} AND last_name={3}.

• Login - When importing contacts, this field is included in the default criteria if it is mapped. For example, login={1}.

• Organization Name - When importing organizations, this field is required and is always included in the default criteria. For example, name={1}.

• Reference # - When importing incidents, this field is included in the default criteria if it is mapped. For example, ref_no={1}.

• Key (configuration setting name)— When importing configuration base entries, these required fields are included in the default criteria. For example, entry_key={Key}.

• ID and Key - When importing configuration base values, these required fields are included in the default criteria. For example, configbase_id={ID} AND configbase_entry_id={Key}.

• Key (message base name) - When importing message base entries, this required field is included in the default criteria. For example, entry_key={Key}.

The custom duplicate criteria is added on top of the above default ones.

See also Answer 4162: Duplicate Criteria in Data Import Wizard

For additional information, refer to the Duplicate Record Handling for Data Imports section in the Online Help User Guide documentation. To access Oracle B2C Service manuals and documentation online, refer to the Documentation for Oracle B2C Service Products.