Observation
On an incoming call, a contact is not found, but it is present in the original data source. Partially, however, the contact is displayed as ~Company.
Possible cause/explanation
- The phone number was assigned to a number field during replication, which is not taken into account during the search.
- Not all records of the source were replicated due to primary key violations.
If the contact is displayed with ~Company only, only the part of the calling number before the extension number matches. Example +49 (8151) 36856-xxx
Procedure
Set checkmark for number search for all filled phone number fields
If the phone number of the source was assigned in the replicator, e.g. to the Tel. company, then this field should also be taken into account in the phone number search.
These hooks are not always set for performance reasons!
Use unique key when replicating data
Example of a replication problem in the source data:
Example
Problematic assignment in the replicator, because the company ID (red in the table above) occurs multiple times:
As a result, not all contacts can be replicated.
Since the employee ID is also not unique across the companies (green in the table above), one can arrive at a unique key in this example, for example, by concatenating the two key fields Company ID and Employee ID:
This is achieved simply by double-assigning fields.
MetaDirectory and DATEV replication – phone number resolution does not always work
