In Data Transforms, you do not need to explicitly map source table columns into fields DataSource and DataSourceObject on the target DLO. These lineage fields are now automatically populated by the transform with values based on the transform.
Note: This was to prevent issues with providing nullable values for these column.
The target table will have these fields with the following values:
DataSource on the target will be the string DataCloudTransforms.
DataSourceObject on the target will set to the Transforms name.
During Activation process of selecting Contact Point Source Priority Order (Screen shot attached):
Users may noticed that you cannot select Source = DataCloudTransform. This is by designed. These source field dropdown values for all contact points is being queried from the Data Source Names that derive from your Data Streams, NOT the Data Lake Object. Since Data Transform can only output to DMO or DLO level, therefore the DataCloudTransform source will not be available for selection. In order to Activate Contact Points Email or Phone that are coming from DataCloudTransform - User must use Source = Any | Email Type = Any. This configuration can be added as a later priority.
By default - For copy field enrichment - there is a default Data Source filter that is present when Data Cloud runs a job to query data from Data Cloud to be copied over to CRM object. The default Data Source query generally looks for Data Source = Salesforce_<Org_Id> Or Data Source = Salesforce_Home. If you are building a CFE (Copy Field Enrichment) out of a DataCloudTransform output - It will filter out qualified record. To avoid this default filter, apply a manual KQ filter for your CFE. This will override the default Data Source filter OR Use Primary Key Match method instead of Unified Lookup match method.
See Screenshot below on how to apply a manual KQ filter:
000397043

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.