Org Chart Global Settings

Org Chart Global Settings allows you to modify the default behavior of several different features. This article details the functionality that can be changed via this custom setting and how you go about doing so.

Functionality that is Modifiable via Org Chart Global Settings

LinkedIn Profile URL and Avatar Functionality

As part of Squivr's Org Chart solution, we include two fields at both the Contact and Account level for storing a LinkedIn Profile URL and the Cards Avatar location. Customers are able to override the fields used for this functionality via the squivr__org_chart_global_settings__c Custom Setting. For example, if you already store the LinkedIn Profile URL in an existing field you can create a Custom Setting record so that Org Chart reads/writes from your field instead of the one that is part of the Squivr package.

5 Star Rating Functionality

Please see 5 Star Rating Functionality for details about the standard functionality vs the enhanced functionality. If you wish to enable the Enhanced 5 Star Rating functionality, set Enhanced Star Rating Menu to true. 

Note: the Enhanced Star Rating Menu field is only relevant when creating a Custom Setting record for the Contact object (Object API Name = Contact)

Sentiment Functionality

Please see Org Chart Contact Sentiment for details about how enabling this setting changes the end-user experience. To enable, set Enable Sentiment Average to true.

Note: the Enable Sentiment Average field is only relevant when creating a Custom Setting record for the Contact object (Object API Name = Contact)

Creating a Custom Setting Record

Navigate to Org Chart Configurations

1. Click the Gear (Settings) icon
2. Select Manage Org Chart Global Settings
3. Select the Object you want to create a setting for
4. Populate the desired fields

*Note: If your LinkedIn URL field has the same API Name as the Squivr LinkedIn field (minus the namespace, LinkedIn__c) please continue reading. Due to a Salesforce shadow issue related to dynamic SOQL in our queries, a namespace always gets added to packaged fields as well as fields that are native to your org. To continue using a different LinkedIn field, you have two options:

Option 1

If possible, update the API name of the field you want to use to be something different than the Squivr field API name. This is the simplest approach but we understand these updates are not always easy or possible.

Option 2: 

1. Do a bulk data load to populate the Squivr LinkedIn field with the data from your LinkedIn field
2. If your LinkedIn field will be updated outside of the Squivr App, you'll also need automation to update our field anytime your field is changed (when updated from the Squivr App, we will write to both fields)