Creating a Hierarchy of Job Roles that Report to the Same Manager

[DMB90]

I am creating a vertical org chart and when I get to a director who has direct reports from various job levels, I want to have a decomposition tree with managers only on one row, supervisors only on one row and staff only on one row but have them all connected to the director. Right now, I am getting a manager and supervisor on the same row and that's not how I want the org chart. I created a manager ID to connect people to their supervisor, but can I perhaps create a more dynamic manager ID so that if it's a certain job level,  they are on a specific level?

[mizan2390 · Accepted solution]

hi @DMB90 

To solve this issue, you need to transition your data from a standard parent-child relationship into a flattened, regular hierarchy.

Right now, your decomposition tree is organizing people based on their "depth" or distance from the top of the chain. If a Manager and a Supervisor both report directly to the Director, the hierarchy considers them both "Level 2" and places them on the same row.
Tabular models do not natively support parent-child hierarchies with variable depths directly in visuals. To force specific job roles onto specific rows, you must flatten the hierarchy by creating dedicated columns for each possible level. To solve this problem heres the DAX pattern that come in handy for you. 
First, generate a technical column that maps the entire reporting path from the top-level director down to the specific employee using the PATH function.

FullPath = PATH ( 'Employee'[EmployeeID], 'Employee'[ManagerID] )

Note: This will create a text string separated by pipes (e.g., DirectorID|ManagerID|StaffID) showing the exact reporting lineage.

Next, create a separate calculated column for every hierarchical level you want in your org chart (e.g., Level 1 for Directors, Level 2 for Managers, Level 3 for Supervisors). You will use the PATHITEM function to extract the ID at that specific level, and LOOKUPVALUE to fetch the employee's name.

Level1_Director = 
LOOKUPVALUE(
    'Employee'[Name],
    'Employee'[EmployeeID], 
    PATHITEM ( 'Employee'[FullPath], 1, INTEGER ) 
)

Level2_Manager = 
LOOKUPVALUE(
    'Employee'[Name],
    'Employee'[EmployeeID], 
    PATHITEM ( 'Employee'[FullPath], 2, INTEGER ) 
)

Level3_Supervisor = 
LOOKUPVALUE(
    'Employee'[Name],
    'Employee'[EmployeeID], 
    PATHITEM ( 'Employee'[FullPath], 3, INTEGER ) 
)

Note: Repeat this for as many levels as you have.

Because your org chart has a variable depth (for example, a Supervisor reporting directly to a Director skips the Manager level entirely), expanding the tree might produce unwanted blank rows for the skipped levels. To hide these empty rows in your visual, you can calculate the true depth of each employee and suppress the visual from drilling down unnecessarily.

NodeDepth = PATHLENGTH ( 'Employee'[FullPath] )

This calculates how many levels deep the specific employee is.

BrowseDepth = 
ISINSCOPE ( 'Employee'[Level1_Director] ) + 
ISINSCOPE ( 'Employee'[Level2_Manager] ) + 
ISINSCOPE ( 'Employee'[Level3_Supervisor] )

This uses ISINSCOPE to dynamically count how many levels deep the user has expanded the decomposition tree.

Instead of using a raw headcount or value in your decomposition tree, wrap your metric in an IF statement that compares the two depths. If the tree is expanded deeper than the employee's actual NodeDepth, it returns BLANK(), which hides the row.

Org Chart Headcount = 
IF (
    MAX ( 'Employee'[NodeDepth] ) < [BrowseDepth],
    BLANK (),
    // Replace with whatever measure you are using for the visual's values
    COUNTROWS('Employee') 
)

By placing your newly created Level1, Level2, and Level3 columns into the decomposition tree in strict order, you force the visual to adhere to your specific levels rather than the raw distance from the Director.

If this solution solve your problem or able to point you out to use in your case. Plese mark this a solved. 

[lbendlin]

So the supervisors are not actually marked as such in your HR hierarchy, and instead are on the same level as employees or managers?

Please provide sample data that covers your issue or question completely, in a usable format (not as a screenshot).
Do not include sensitive information. Do not include anything that is unrelated to the issue or question.
Please show the expected outcome based on the sample data you provided.

Need help uploading data? https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-...
Want faster answers? https://community.fabric.microsoft.com/t5/Desktop/How-to-Get-Your-Question-Answered-Quickly/m-p/1447...