Match-up Types

No. Found -> Change

The primary key of the external record is searched for in the local database.

• If a record is found with the same primary key, the external and internal records are merged, i.e. the internal record is updated with the most recent field contents.
• If no record is found with the same primary key, a new record is added. If further match-up conditions have been defined, these are applied.

  Usage: Unique primary keys, no duplicates expected.

No. Found -> Compare Name/Addr.

The primary key and name and address of the external record are searched for in the local database.

• If a record is found with the same primary key, the name and address in the external and internal records are compared. The records are only merged if the record is judged to be identical after comparing the name and address. Otherwise the record is rejected.
• If a record is found with the same primary key where the name and address does not match the data in the external record, the record is handled differently based on the execution type (Execution field in the Communication info area):
  • The record is rejected as false if the communication process is automatic and/or the option No manual control is enabled.
  • If the communication process is started directly from the Communication info area using manual and/or manual/automatic execution, and the option No manual control is disabled, you can merge the record with the internal record with the same primary key, see Communication with Manual Match-up.
• If no record is found with the same primary key, a new record is added.

  Usage: No unique primary keys.

No. not found -> New

The primary key of the external record is searched for in the local database.

• If a record is found with the same primary key, the external and internal records are merged, i.e. the internal record is updated with the most recent field contents.
• If no record is found with the same primary key, a new record is added without matching up the records further.

  Usage: Unique primary keys, no duplicates expected.

Name/addr. identical -> Change

The name and address of the external record is searched for in the local database.

• If a record is found with the same name and address as the external record, the records are merged, i.e. the internal record is updated with the most recent field contents.
• If no record is found with the same name and address as the external record, the record is treated as follows depending on the execution type (entered in the Execution field in the Communication info area):
  • If the communication process is started automatically and/or the No manual control option is enabled, the record is added without a prompt.
  • If the communication process is started directly from the Communication info area, or the execution type is "Manual/Autom.", similar internal records are listed, see Communication with Manual Match-up.

Name/addr. identical -> New

Use this option to check for records with the same name and address, and to add the record even if an identical record is found.

Usage: When individual companies should be present in the database multiple times (e.g. for billing purposes).

No. Similar -> Log

If the external and internal keys are identical but the name and address are different, the record is saved to a log file (sim.*). This file then needs to be manually imported and matched up, see Inputting SIM files.

Name/Address Similar -> Log

If internal records are found with a similar name and address to the external record, the external record is saved to a log file (sim.*)

-> Log

Records are not matched up any further, but are immediately written to a log file (sim.*).