Skip to main content

Unable to Find Matching Record in Destination System

When SyncHive encounters the error "Unable to find a matching record in the destination system," it signifies that the document being processed includes an ID that does not exist in the destination system. This documentation provides insights into understanding, handling, and resolving this issue.

Error Description​

Consider the following Product document as an example:

{
    "@type": "Product",
    "name": "T-Shirt",
    "description": "Classic Organic T-Shirt.",
    "externalIdentity": [
        {
            "@type": "ExternalID",
            "internalType": "Product",
            "externalSystemCode": "Shopify",
            "externalId": "2364423996"
        }
    ],
    "alternateId": "448114" <-- This ID does not exist in the destination system
}

In this scenario, the alternateId (448114) in the document does not correspond to an existing record in the destination system.

SyncHive Handling​

SyncHive addresses this situation by saving the record but refrains from integrating it into the destination system. This approach ensures that inaccurate data is not transferred to the destination, maintaining data integrity.

Occurrence and Resolution​

When Does This Happen?​

  1. Find the Record in the Destination System:​

    Verify the existence of the record with the specified ID in the destination system.

  2. Check if the ID is Correct:​

    Confirm the accuracy of the ID in the document against the destination system's records.

  3. Update the Record in the Source System:​

    If discrepancies are found, update the record in the source system with the correct information.

  4. Clean Up Incorrect Data:​

    To prevent potential duplication and maintain data accuracy, perform cleanup activities for incorrect data.