You want to synchronize, for example, locations from a csv file to D1IM.
For this purpose you create a synchronization project with an object matching rule for AccountNumber(D1IM) <-> ProfitCenterID(CSVFile).
However you have occasional entries where locality appears more than once in your csv file.
For loc2 the processing is cancelled completely with the following error message:
Warning The object matching rule (AccountNumber <-> ProfitCenterID)
supplied the following 2 objects with the same key
(00000010). These objects were ignored.
You need to have the loc2 entry not skipped completely, but inserted and updated.
The synchronization works with objects. These are loaded on 2 sides into sets and then synchronized.
The sets of objects need to be unambiguous (no duplicate identities). A synchronization is not able to deal with duplicate identities as described above, therefore the synchronization of such entries are ignored.
The CSV files need to be cleaned up from any duplicate entries before being used for synchronization.