Role Hierarchy Requirements for Templated CRM Analytics Apps

Templated CRM Analytics Apps, including Sales Analytics, Service Analytics, and Financial Services Cloud Analytics, require a properly configured Role Hierarchy to accurately reflect team structure, enable row-level security, and support correct roll-up calculations in dashboards.

If Role Hierarchy requirements are not met, dataflow jobs fail. This error typically appears as:

Something went wrong while executing the FlattenRole node: parent_field does not have any data.

Requirements

• Role Hierarchy must have at least two levels
• Users must be assigned a Role
• Each level in the hierarchy must have at least one User assigned

Impact

Not meeting these requirements may cause the dataflow to fail. An incomplete role hierarchy may also result in unexpected visibility issues in datasets and dashboards — this can manifest as seeing too many records, or not seeing all expected records.

Exceptions

Sales Analytics no longer requires Role Hierarchy. Sales Analytics detects if the environment uses Role Hierarchy, and if not, the setup wizard removes all references to Role Hierarchy. Any page that previously referenced Role will reference Opportunity Owner instead.

Einstein Activity Capture and High Velocity Sales use Role Hierarchy to control visibility. If role hierarchy is used, users see data only for activities they are involved in and that users below them in the hierarchy own. If role hierarchy is not used, users see all activity data in the dataset.

Event Monitoring Analytics App can bypass this error by adding a dummy two-level Role Hierarchy with or without users assigned. Review the related Known Issue for more information.

Note: Partner roles might not be visible in the UI. To check for roles, run a SOQL query selecting Id, Name, and ParentRoleId from the UserRole object.