Loading
About Salesforce Data 360
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Enrichment Considerations

            You are here:

            1. Salesforce Help
            2. Docs
            3. Data 360

            Enrichment Considerations

            Learn vital information about security, data storage, cost, deletion, and other considerations before you create enrichments to use Data 360 data in your org.

            Supported Source and Target Objects for Related Lists

            You can create a related list enrichment on these target objects.

            • Account
            • Contact
            • Lead

            Your related list enrichment queries records from these source objects.

            • A DMO with the category Engagement, Profile, or Other that has a relationship to the Unified Individual DMO, Unified Account DMO, Individual DMO, or Account DMO. The DMO’s source data can be from other Salesforce orgs or from external data streams.
            • A Unified contact point DMO, such as contact point email.
              Note
              Note The unified contact point DMO is the only derived DMO that you can use in your related list enrichments.
            • On Vehicle objects in Automotive Cloud, you can use any source DMO with an ID that uniquely identifies the vehicle. For example, you can use a vehicle identification number as a unique identifier to display vehicle telemetry data from a DMO as a related list on vehicles.

            Supported Source and Target Objects for Direct-DMO Related Lists

            You can create a direct-DMO related list enrichment by using direct relationships between DMOs and Salesforce objects without the need for identity resolution. You can create a direct-DMO related list enrichment on these target objects.

            • Account
            • AssetAccountParticipant
            • AssetContactParticipant
            • AssetMilestone
            • Case
            • Contact
            • Contract
            • FinancialAccount
            • Fleet
            • Lead
            • LeadLineItem
            • LeadPreferredSeller
            • Opportunity
            • OpportunityPreferredSeller
            • Order
            • Product2
            • Vehicle
            • Work Order
            • Work Order Line Item

            Your direct relationship enrichment can query records from the source DMO that’s connected to the Salesforce object through the direct relationship. ‌The direct relationship matches the DMO records with the Salesforce object records by using an ID or string field.

            For considerations, see Direct-DMO Related List Enrichment and Merged Salesforce Records Considerations.

            Supported Source and Target Objects for Copy Fields

            You can create a copy field enrichment on these target objects.

            • Account
            • Asset
            • Case
            Note
            Note If you add a copy field enrichment to the Case object, auto-assignment isn’t supported for cases. Also, feed tracking isn’t supported for enriched objects. See Feed Tracking and Assign Cases.
            • ClinicalServiceRequest
            • Collection Plan
            • Contact
            • Contract
            • Custom Object
            • Invoice
            • Lead
            • Opportunity
            • Order
            • Product
            • Quote

            Your copy field enrichment copies data from either a DMO or from a calculated insight object (CIO). You can use any one-dimensional or multi-dimensional aggregatable CIO as a source object. You can use these DMOs as a source object.

            • Mapped DMOs—If the DMO’s source data is an external data stream, select accelerate when creating the data stream so that the external data is cached in Data Cloud.
            • Unified Individual
            • Unified Account

            With copy field enrichments, data for the correct person or account is copied from Data Cloud to your org. If the source DMO in Data Cloud doesn’t have a 1:1 relationship with a unified object, then copy field enrichments return records that match the primary key of your org’s target object.

            Supported Data Types for Copy Field Enrichments

            When creating a copy field enrichment, you can copy data from these DMO/CIO source fields.

            • Number
            • Text
            • Date
            • DateTime
            • Email
            • Phone
            • Url
            • Percent
            • Boolean
            • Currency

            You can copy values into these target fields on your CRM object.

            • Double
            • Text
            • DateOnly
            • DateTime
            • Email
            • Phone
            • Url
            • Percent
            • Boolean
            • Currency

            Currency Fields for Copy Field Enrichments

            You can copy financial data from data model objects (DMOs) into Salesforce objects using currency fields in copy field enrichments.

            Consider these guidelines and limitations.

            • Multi-currency orgs aren’t supported.
            • If there’s a mismatch between the org currency and the currency coming from Data 360, those records aren’t copied.
            • Changing the org currency with an active currency copy field enrichment doesn’t trigger incremental Change Data Feed job execution.
            • You must redo the currency copy field enrichment setup if the org currency changes while there is an active currency copy field enrichment to avoid data corruption issues.

            Security

            Permissions that are set on the parent object (Contact, Lead, or Person Account) in your org restrict access to the related list or copy field in your record home page.

            You can restrict who can view a related list so that:

            • Everyone who can access the object record home page can see the related list.
            • No one who can access the object record home page can see the related list.
            • Only users who have permissions to view that parent object in your org can see the related list.
            • Only users who have specific permissions for each data space scope can see the related list.

            If you restrict access so that a user who has access to the object record home page doesn’t have access to the related list data, the related list appears blank.

            For data spaces, the standard Salesforce security policy of “most restricted access wins” doesn’t apply to the data shown in related list enrichments. All information within a selected data space is accessible, regardless of additional data restrictions placed within Data Cloud. To restrict the data that can be viewed, create a dynamic related list and filter on the data space.

            You can control user access to data space aware objects and features by setting the object permissions and feature permissions in the user’s permission sets. For more information, see Data Space Aware Objects and Features.

            Data Loss

            If you map a copy field enrichment to an existing field in an org, the data in the field is overwritten with data from Data Cloud. Depending on the ingestion and sync options configured for Data Cloud, it’s possible for data changed in an org field to be overwritten before the data is ingested into Data Cloud, causing data loss.

            To avoid possible data loss, consider these options.

            • Map the copy field to a new field that only contains Data Cloud data, instead of an existing field on a Salesforce object where data is entered. For example, if Contact has a Nickname field where service reps can enter a nickname, create a new Preferred Nickname field for data from Data Cloud. Data Cloud data is harmonized and more likely to show clean and accurate data. You can control whether the last entered nickname or the most frequently used nickname is used in resolving different values in Data Cloud.
            • Don’t use scheduled ingestion for data streams from your org. Instead, create a workflow to allow ingestion triggered by data changes for fields that you’re copying data into.

            For example, if a customer calls into any service center to change their last name, you want the latest data to be available to all of your service reps, no matter what business unit they work for.

            You set up a data stream from your org to Data Cloud, scheduled every 15 minutes. You create an enrichment that copies data from Data Cloud into the Last Name field in your org. The service rep changes the customer’s last name from Alders to Mayfair in the Last Name field, which is a copy field. Salesforce syncs the field data for the copy field before scheduled data ingestion, overwriting Mayfair with the original value of Alders. The new value of Mayfair is unrecoverable.

            To keep data from being overwritten, you create a flow to allow ingestion to be triggered when changes are detected for the Last Name field.

            Data Actions and Data Targets

            Copy field enrichments impact the total number of data actions and data targets available. Each copy field enrichment uses one data action and one data target available with your Data Cloud license. The number of available data actions and data targets can be found on the list of enrichments for the object.

            Data Latency

            When you click to see more information in a related list, the list queries Data Cloud for more information. Data in the component is displayed in near real-time. However, if you specified more than the default date range of 7 days of data, the related list can experience significant latency, depending on the amount of data retrieved. You can reduce the date range or add filters as part of your related list enrichment to improve latency.

            Copy field enrichments use a batch job to sync information between Data Cloud and your org records. Depending on the number of records being processed, there’s some data latency. The initial load of data takes hours or days, depending on the number of records, but subsequent syncs only update changed records and are quicker.

            Dynamic Related Lists

            You can create a dynamic related list from the related list created by the related list enrichment. With a dynamic related list, you can override the default 7-day limit of data returned for a related list enrichment and restrict the data shown in the list.

            Lightning and Lightning App Builder

            Related list components in the Lightning App Builder and on Lightning record pages have some limitations for related list enrichments.

            • The Related List - Single component and the Related Lists component don’t show previews of Data Cloud related lists in the Lightning App Builder.
            • In the Lightning App Builder, the Related List Quick Links component doesn’t show the record count for Data Cloud related lists. On the record page, when users hover over a Data Cloud related list in the component, the list overlay doesn’t show any related records.

            Limits for Related List Enrichment

            • For related list enrichments, the maximum number of related lists depends on the maximum number of lookup relationships you can create in your Data Cloud org. The upper limit for an org is 10,000.
            • You can create related lists for all data types, except for the Array of Floats data type.

            Related List Date Range for Engagement Data

            By default, related list enrichments that contain engagement data return data from the last 7 days. You can modify the default date range by using a date filter when you create or edit an enrichment, or by creating a dynamic list. Keep in mind that a longer date range can make the related list significantly slower because the amount of data to display can be large.

            Person Accounts

            When creating a related list enrichment for the Contact object, if you have person accounts enabled in Setup, you see an option to add them to the Person Account record home page. The Person Account related list is based on the Contact or Account object. For tips on which ID field to use for mapping, see Data Cloud: Person Account Related List Mapping Requirement.

            Person account fields that are contact fields, not business account fields, can’t be used in copy field enrichments. These fields are identifiable by a prefix Person or suffix _pc on the field name.

            Use Person Accounts as a Target for Direct-DMO Related List Enrichments

            Starting in Winter ’26, you can select Person Account Fields when configuring a Direct-DMO Related List Enrichment in a Person Account enabled org. You can use fields from either the underlying Account or Contact objects as the matching fields, providing greater flexibility to link data between Data Cloud and your CRM.

            Direct-DMO Related List Enrichment and Merged Salesforce Records Considerations

            Merged Salesforce records can cause issues with direct-DMO related list enrichments if they reference the Salesforce record ID. When duplicate accounts, contacts, or lead records are merged by using duplicate rules, one of the records is deleted and its ID is no longer valid because the record no longer exists. If a related list enrichment uses a DMO relationship that matches records based on IDs, and it references the deleted Salesforce record ID, the related list enrichment doesn’t display all the related data.

            The solution depends on the type of connector used.

            • If a Salesforce CRM Connector is set up, refresh the data stream. This refresh updates the record ID on the Data Cloud DMO records.
            • If a connector is used to an external data source, such as S3, update the IDs in the external data source. The external connection uses one of these Data Cloud connectors.

            Here’s an example of a record merge scenario. Say the Salesforce admin sets up a relationship between the Contact Salesforce object and the Email Engagement DMO and relates the records based on the Contact.Id and the EmailEngagement.ssot__IndividualId__c fields. When a contact record with an Id of 2 is merged with a contact with an Id of 1, the system deletes the contact with Id of 2. As a result, the Email Engagement records that reference the IndividualId__c field of 2 aren’t displayed on the enriched contact with Id of 1 after the merge. To fix this issue, update the DMO data so that the Email Engagements that are associated with IndividualId__c of 2 are associated with IndividualId__c of 1.

            This consideration affects only direct-DMO related list enrichments that use an ID field on the Salesforce object. It doesn’t affect other types of enrichments or direct-DMO enrichments that aren’t based on a CRM object ID field.

            Limits for Copy Field Enrichment

            The maximum number of copy field enrichments is limited by the maximum number of data actions and data action targets for your org.

            The maximum number of fields you can copy for a single enrichment without experiencing performance impacts is the maximum number of custom fields on an entity. However, you can create multiple enrichments for the same objects if you want.

            Excluded Fields for Copy Field Enrichment

            Salesforce excludes fields that aren’t supported for copy field enrichment. The excluded fields aren’t available as target fields for copy field enrichment. They’re separate from incompatible fields.

            Technical Considerations for Copy Field Enrichment

            These technical considerations are crucial for a successful Copy Field Enrichment implementation.

            • Data kit compatibility: Data kits are a critical functionality for many users. However, the current compatibility between enrichments and data kits is unclear. Further investigation is recommended to ensure seamless integration.
            • Impact on Existing Workflows: Implementing an enrichment can impact existing data processing workflows. Thoroughly evaluate potential disruptions and develop mitigation strategies if necessary.

            Full Sync Limits

            A full sync job can run for a maximum of 24 hours. The number of records that can be processed is 60–100 million, depending on the environment in. Production environments can generally process more records.

            Troubleshooting Enrichments

            Data in the org depends on data space, object, mapping, and data ingestion in Data Cloud.

            If your enrichment doesn’t behave as expected, make sure that:

            • The object and the data space configured for it haven’t changed.
            • The data stream for the objects is connected successfully and ingesting data.
            • You specified the correct key qualifier. You don’t usually require a key qualifier. However, if you specified the wrong key qualifier, it can cause the wrong data to be copied over. You need a key qualifier only in the rare case that data from your org isn’t ingested directly by using the CRM connector but via another system or service.
            • If a user notices that a related list is blank, make sure that they have data space access control for any permission sets assigned to them.
             
            Loading
            Salesforce Help | Article