Salesforce Data 360 (formerly Data Cloud) uses Data Model Objects (DMOs) to represent entities like individuals, accounts, or custom objects. These are connected through relationships, which define how data from one DMO relates to another.
As detailed in Data 360 Limits and Guidelines, there is a hard limit of 1,050 fields per data model object. Each outbound relationship (from the source DMO to a target DMO) creates a custom field definition on the source DMO that contributes to this limit. Custom fields include both explicitly created fields and those generated by relationships, such as those from activations or Calculated Insights (CIs).
This limit is critical in scenarios involving activations or CIs, particularly when using Data 360 Loyalty as the activation target. For example:
When the limit is exceeded, attempts to create or save activations fail with errors like "Unable to create lookup for relationship" or "CustomFieldLimitExceededException" (Error ID: CustomFieldLimitExceededException). No warnings appear in the UI until the limit is hit, and the backend custom field count may not be visible in the standard object limits view. A work item is under investigation to improve UI error messaging.
Note: Inbound relationships (to the DMO) do not contribute to the custom field count on that DMO. A planned fix aims to reverse the relationship direction for Loyalty activations, reducing the impact on the source DMO’s custom field limit. For more on DMO relationships, see Data Model Object Relationships.
To resolve or prevent issues caused by exceeding the CFD limit:
If the issue persists after these steps, contact Salesforce Support with details on the affected DMO, segment, and activation target. For general considerations on activations with related attributes, see Considerations for Selecting Related Attributes in Data 360 Activations.
005167053

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.