Loading

Data 360: Full Refresh for CRM, SFMC,WebSDK or Ingestion API Data Streams

Data pubblicazione: Jan 20, 2026
Descrizione

Data from Salesforce CRM or SFMC is loaded into Data 360 in a frequent, light-weight, incremental fashion so that your Data 360 data stays up to date with the latest changes. On a less frequent interval, the entire data stream is reloaded from scratch in the Full Refresh ("Day Zero") data load as an extra precaution to avoid inconsistency. In some scenarios, there may be a benefit from forcing a Full Refresh earlier than scheduled:

  1. You added, removed, or edited a field in your Data 360 data stream and for some reason no Full Refresh was initiated. (i.e. normally you should see the changes reflected in Data 360 within an hour, and the reported number of rows affected is large since it should be your entire data stream)
  2. You have deleted a large number of rows in a short period of time, and need this data reflected in Data 360 before the next regularly scheduled Full Refresh.

Data loaded from Ingestion API is unable to have a Full Refresh manually forced as it is configured to always be upserts. When a new formula field is added, the recommended approach is to re-ingest all previously ingested data. An alternative is to utilize Streaming Data Transforms. 

Risoluzione

With the November 2025 Monthly Release, you can now manually refresh SFMC Data Extension Data Streams as well as CRM Data Streams. 

Note: When a full refresh job is initiated from the backend, you might notice a single failure entry in the Processing history. This occurs because the Upsert job is canceled to allow the full refresh job to proceed. 
 

For Ingestion API/ Web SDK, you can follow these steps to use Data Transforms:

  1. Create a new DLO, DLO2
  2. Create a new streaming transform that includes the new formula field calculation
  3. Use the source DLO1 as the input for this streaming transform, and DLO2 as the output
  4. When this transform is saved, it will immediately process all records from DLO1 and write them to DLO2. Data records will be processed per the SQL used in the transform
  5. Change all field mappings from DLO1 to DLO2


Otherwise, re-ingesting all previously ingested data to ensure all records are updated for Ingestion API Data streams.
 

Numero articolo Knowledge

000389693

 
Caricamento
Salesforce Help | Article