Data 360: Impact of Data Space Filters on Data Stream Counts

Add Data to a Data Space Using Data Lake Objects outlines how to configure a Data Space filter on a Data Lake Object. In this Help documentation the following note is added:

The data space record count filter does not impact DLOs. With the filter on, DLOs still display their total number of records that are ingested from the data stream.

To expand on this point, when a Data Space filter is added on a data stream's DLO, this does not prevent records from being ingested from the connected data source (i.e. it does not pre-filter the records before they are ingested into Data 360 (formerly Data Cloud) instead it determines which of the records in the DLO are available on the associated Data Space.

Salesforce CRM Data Streams

When creating a Salesforce CRM Data Stream, on the final step in the creation wizard before clicking Deploy, there is the option to Set Filters when you choose the Data Space the Data Stream is associated with. Configuring a filter here does not prevent all records of that object from being ingested into Data 360. Instead it creates a Data Space filter on the Data Stream's Data Lake Object.

After creating a Salesforce CRM Data Stream with a filter, you will still see all records of that object getting ingested into Data 360. This will be reflected in the Total Records count you see when looking at the Data Stream or its Data Lake Object. The Data Space filter applied here is reflected when you try to access records from a data-space aware context e.g. if you go to Data Explorer, choose the Data Space and then viewed records on the Data Lake Object in the context of that Data Space.

Currently it is not possible to pre-filter records from Salesforce CRM so that only records that meet a filter criteria are ingested into Data 360.