Loading

Data 360: Ensuring Consistent Updates from Unified Profile to Copy Field Enrichment Objects

Publish Date: May 26, 2026
Description

In certain scenarios, updates made to the Unified Profile table do not fully sync to the target table (e.g., the Contact table) during a Copy Field Enrichment.

The Data Action tied to this flow monitors updates in the Profile table and joins them with the Identity Link table to locate the correct source records. However, this process can fail due to three primary limitations:

  1. Asynchronous Identity-Resolution Process: The backend processes updating the Profile and Identity Link tables do not run synchronously. If the Data Action fetches an event from the Profile table before the Identity Link table has finished updating, the corresponding source records will be missed.
  2. Partial Updates: Occasionally, updates only trigger on one table. If the Identity Link table updates but the Profile table does not (or vice versa), the Data Action will not register the complete change.
  3. Processing Latency: Data Actions experience a lookup table retrieval latency of over 10 minutes, widening the time window where source records can be missed.

 

Resolution

Workaround: Using a Calculated Insight for More Reliable Updates

To improve data consistency, customers can create a Calculated Insight based on the Identity Link table and use it in the CFE flow.

Steps to Implement the CI Solution

  1. Create a Calculated Insight that aggregates the required data

    • Schedule it to run every hour (minimum possible interval) to ensure more frequent updates.

    Sample CI Query:

    SELECT  
   FIRST(UnifiedLinkssotIndividualRs01__dlm.UnifiedRecordId__c) AS UnifiedRecordId__c,  
   UnifiedLinkssotIndividualRs01__dlm.SourceRecordId__c AS SourceRecordId__c  
FROM  
   UnifiedLinkssotIndividualRs01__dlm  
GROUP BY  
   UnifiedLinkssotIndividualRs01__dlm.SourceRecordId__c

  2. Create a Copy Field Enrichment to copy UnifiedRecordId__c from the CI to the Contact table

Limitations:

  • The CI can only run once per hour, introducing a potential worst-case delay of 1 hour for updates.

Knowledge Article Number

004464194

 
Loading
Salesforce Help | Article