The purpose of this article is to outline expected behavior and best practices when working with large hierarchies. Org Chart has functionality (configuration, search, layout options and template styles) to help you navigate complex hierarchies efficiently but, as a native application, we are beholden to Salesforce's governors and limits. Platform limits aside, our experience is that at a certain point, presenting a user with the full data set impacts usability.
Squivr Terminology
The phrases we use in reference to Org Chart, it's functionality and expected behavior.
Phrase | Squivr Definition |
Top Level Contact | A Contact that has one or more subordinates and does not report to another Contact |
Independent Contact | A Contact that does not have any subordinates and does not report to another Contact |
Org Chart Canvas | The main area of the Org Chart component/page where the Account and Contact cards are displayed |
Detail Panel | The panel that opens when an Account or Contact card is double clicked |
Control Bar | The list of icons in the upper left of the Org Chart component/page |
Org Chart Behavior for Possible Hierarchy Shapes & Sizes
Applies To | Shape & Size | Initial Load Behavior |
Account View |
<=200 total records <=5 Account relationship levels |
|
Account View |
<=500 total records <=200 independent contacts <=5 Account relationship levels |
|
Account View |
>200 independent contacts |
|
Account & Contact View |
>500 total Org Chart Canvas records <=5 Account relationship levels |
|
Account View |
>1,000 top level Account Contacts* <=10,000 top level Account Contacts* *regardless of Parking Lot status |
|
Account View |
>5 Account relationship levels |
|
Account View |
>10,000 top level Account Contacts* *regardless of Parking Lot status |
|
Contact View |
>10,000 top level Account Contacts* <=500 subordinate Contacts *regardless of Parking Lot status |
|