Unlock the Secret CRM Analytics Feature They Left Out of the Documentation!

If you're interested in setting up role hierarchy in your CRM Analytics (CRMA) dashboards or know everything about CRMA, this article is perfect for you. Wondering when this feature might come in handy?

1. When you want to create a filter that works based on role hierarchy.

2. When you prefer to display user names instead of role names.

3. When you need to distinguish between records that belong to individual users and records associated with their teams.

How it looks?

Role Hierarchy filter in CRM Analytics


This is a live (yes, works in real-time) and it takes the role hierarchy, transforms it, and displays so you get a picklist with different options to choose from.

In the query, you also get lots of other fields like a multivalue of role hierarchy IDs and other fields which are helpful for filtering. All of them can be used to get proper filtering based on the criteria that you have in your dataset. Here is a full table with some sample data from a demo org:

Query results from Role Hierarchy


How to create it?

Currently it’s a hidden feature and CRM Analytics does not provide any documentation, however Salesforce support is helpful in providing more information about the details of that feature. We expect that it will be fully revealed in the upcoming releases.

So, to create it, you need to:

  • Create any query as a placeholder.

  • Open that query with advanced editor

  • Delete everything and past the following code:

{
    "filterField": "roleDeveloperName",
    "hierarchyType": "RoleHierarchy",
    "query": {},
    "selectMode": "singlerequired",
    "type": "hierarchy"
}

You’ll see that your query looks like this:

Okay, now let's put it on the dashboard:

  1. Add a List widget to the dashboard canvas.

  2. Take this query and drop it onto the widget.

  3. Customize how it looks and pick 'displayName.'

  4. That's it! Your filter is on the dashboard, and you can check it out.

For it to work with your specific requests, it's a good idea to use Connected Data Sources. You can also use bindings.


What's in this filter?

It's difficult to say because Salesforce hasn't provided any documentation. From what we've discovered, it seems to be a hierarchy that includes the current user, their team, and individuals or teams one level below in the hierarchy, depending on the structure. This hierarchy also includes the Partner hierarchy.

What are the problems with that feature?

  1. You can't change the query, like removing the Partner hierarchy. You can only set a limit on how many records it shows.

  2. There's a weird dot in front of the word "Team."

  3. The query is slow. Our tests consistently show it takes over 1 second to run, even on an empty dashboard.

If you want to find out more about this feature or see what you can create using it, just send us a message: hello@cloudandberry.com

Doesn't work? Having trouble with connecting data sources? Get a free PDF on how to connect them!

    Previous
    Previous

    UX Wednesday: 3 reasons why we avoid pie charts

    Next
    Next

    The story behind Cloud & Berry