Match-up Logic for other Info Areas

Match-up Rules for Dependent Info Areas

When importing supplementary information, information needs to be provided with which the external data can be linked to companies and/or persons already in the Aurea CRM database. If the supplementary information is person-related, you need information on both the company and the person. If the information is company-related, you only need information on the company.

• If new data should be added to dependent info areas when importing, this data should either be matched up with data in the parent info area (with data in the dependent info areas being added as new records) or the parent record must first be added as a new record.
• If data is matched up in one info area, data in parent info areas is not updated. All info areas that receive imported data need to be matched up separately using a suitable match-up key.
• Some import keys are not tested by Aurea CRM to verify that they are unique. If several records with the same key are stored in the system, the first record that is found is used to match up the external data. In this case, the external system needs to guarantee that keys are unique (e.g. Head Ext.Key in the Order info area)
• If a match-up key does not contain the key of the parent info area, but the key has been defined in the import file, the external system needs to guarantee that these keys match. Otherwise the record is imported incorrectly; e.g. an order by company X is assigned to company Y after importing.
• If an info area is rejected as false in a match-up line, all subsequent dependent info areas are rejected as false in this line.
• Data for several info areas can be imported in one line in the import file. If the data in one info area is identical to the data in the line immediately above, the info area is automatically recognized as identical to the one in the line above, and is not displayed in the communication log file, irrespective of whether match-up is activated for this info area. If even a single field differs, the data is treated as a new record.
• If all of the fields in a line relating to a record are empty, the record is not included in the log file. Subsequent records in this line cannot be matched up via this record.

Match-up using Specific Indices

The following info areas are first matched up using the primary key. If the serial number used to form the primary key is not included in the imported record, the record is matched up using a specific index. If this index is not unique ([DUPLICATE] in the Properties column in the data model), the first record that is found containing the same index values is used to match up the imported record.

All indices for all info areas can be found in the data model, see Index in the CRM.core Administrator Guide. You can output all indices to a file using the -m or -- writexmldef parameters, see mmba.exe Parameters in the CRM.core Administrator Guide.