This topic focuses on using the search then create or update record API call to create new records in the SOR. However, this pattern can be followed for any update to records in the SOR provided that the update is also made in the source record.

Requirements

New and updated records must be added to source datasets in the data product (with a stable primary key and using the provided sourceId field). This ensures the rec_id is persistent when the SOR is updated with the latest outputs from your data product.

In the example below, source_A is the name of the source inside of the data product configuration. A record exists in that source with the primary key value of 1234.

Understanding Record Creates and Updates

1. New records are created in both the SOR, via the search then create or update record API call, and in the source dataset for the data product for the purpose of batch enrichment and clustering. The rec_id of the record in the SOR is persistent and is not deleted when the batch data product is run.
2. Retired tamr_ids (golden record IDs) are available in the record history and can be used in search.
3. The search then create or update record API call creates new records if no match is found.
4. The search then create or update record API call updates a record if a match is found. It updates only attributes in a record where the value is null (only the new values will be added). Otherwise the update will happen after the next data product refresh, taking into account the data product’s consolidation logic.