Here is some new query samples on how DAX hierarchies work. And this time it will work 🙂
Id did a little modification of the model. I had to make a new hierachy in the employee table.

Then you will have to deploy the model to the server.
My sample query looks like this:
DEFINE
MEASURE 'Employee'[Employeelevel] =
PATHLENGTH (
PATH ( Employee[EmployeeKey], Employee[ParentEmployeeKey] )
)
MEASURE 'Employee'[ParentEmployee] =
LOOKUPVALUE (
'Employee'[Last Name],
'Employee'[EmployeeKey], PATHITEMREVERSE (
PATH (
'Employee'[EmployeeKey],
'Employee'[ParentEmployeeKey]
),
2,
1
)
)
MEASURE 'Employee'[PathReverse] =
PATHITEMREVERSE (
PATH (
'Employee'[EmployeeKey],
'Employee'[ParentEmployeeKey]
),
2,
1
)
MEASURE 'Employee'[Path] =
PATH (
'Employee'[EmployeeKey],
'Employee'[ParentEmployeeKey]
)
EVALUATE
FILTER (
SUMMARIZE (
'Employee',
'Employee'[EmployeeKey],
'Employee'[Last Name],
"Sales", 'Reseller Sales'[Reseller Total Sales],
"Path", 'Employee'[Path],
"PathItemReverse", 'Employee'[PathReverse],
"Employeelevel", 'Employee'[Employeelevel],
"ParentEmployee", 'Employee'[ParentEmployee]
),
ISBLANK ( 'Reseller Sales'[Reseller Total Sales] ) = FALSE
)
ORDER BY 'Employee'[ParentEmployee], 'Employee'[EmployeeKey]
And the result looks like this

To verify the result I made an Excel pivot.