All Ideas

Idea Details

Post an Idea

This idea has been merged into another idea. To comment or vote on this idea, please visit Increase limit of Object References / Spanning Relationships.

0 Points voting closed

Merged

Nancy McGarrity

You have reached the maximum number of 12 object references on Case

Salesforce Platform, Applications, Customization, Salesforce Ideas

Please increase this limit as it severely impacts out ability to customize Salesforce especially on Cases which is one of our main objects. It allowed me to add a lookup field without errors. But when I try to add a formula field it errors.

· Flag

Latest Comment from Salesforce

Shannon Hale - 9 years ago

Hi tucsoncoyote,

I'm the product owner for this area.

This limit may be increased to a maximum of 15 through Salesforce support. However, it cannot be increased beyond that at this time, and increasing it above 10 may impact performance in formula fields, reports and page views. Due to the performance implications and the development and testing involved, it is not on our roadmap for the next year to raise the hard limit of 15.

I know that's not the response you're looking for right now, but here's some information that might help you reduce your object references. Even if you request a limit increase to address your immediate needs, you may wish to consider these as longer term solutions.

The object references (aka "spanning relationship") limit is based on the number of unique relationships referenced in formulas on an object: formula fields, workflow rules, validation rules, assignment rules, escalation rules, and auto-response rules. It doesn't include lookup filters, and it's not related to lookup fields. If you click the "Show references" link in the error message, it shows a list of the components that are contributing to the count.

Each relationship traversal is one unique relationship. For example, from the Case object, Parent.CaseNumber would be one unique relationship (Case-Case). Account.CreatedBy.LastName would be two unique relationships (Case-Account-User). Account.LastModifiedBy.LastName on the same Case object would be one additional traversal (the relationship to Account already exists). Global merge variables (e.g. $User.ProfileID) don't count towards the limit.

The alternative to spanning relationships is to use Apex or VIsualforce, which are tooled to handle more complexity than the formula engine is. Start by looking at the "Show References" list and see if you have validation rules you can move to a trigger. Or consider if there are other ways to expose data in formula fields -- for example, using the detail hover on a lookup field for information 1-2 levels away, if you want to see information on the page layout but don't need to report on it.

I hope that helps you out a bit.

--Shannon