Loading

Data 360: Understanding Discrepancies in Record Counts for Target DLO from Streaming Data Transformation

Publiceringsdatum: Dec 5, 2025
Beskrivning

In the Engagement DLO, two fields determine the uniqueness of each record: the primary key and a date or date-time field. When an Engagement DLO is used as the source for a streaming data transformation, the total number of records in the target DLO might not match the source DLO, even if both are of the Engagement type.

The reason for this difference lies in how the streaming data transformation identifies and handles duplicate records. During transformation, only the primary key is considered to determine record uniqueness. As a result, if the source DLO contains multiple records that share the same primary key but differ in other fields (such as the date or date-time field), the transformation process will discard these duplicates. Consequently, fewer records will appear in the target DLO.

This can be particularly problematic in scenarios where both the primary key and the date field should be used to maintain uniqueness. If only the primary key is referenced, important variations between records might be lost.

Lösning

To resolve this issue and ensure accurate record counts in the target DLO, you may try the following approach:

Concatenate Fields for Uniqueness:

Modify the transformation to combine two columns, such as the primary key and the date (or date-time) field to form a composite key that guarantees the uniqueness of each row.

This ensures that the transformation recognizes differences between records that share the same primary key but have different date values.

Knowledge-artikelnummer

002772120

 
Laddar
Salesforce Help | Article