Creating a Level-Based Hierarchy (CX) | Experience Community
Skip to main content

Creating a Level-Based Hierarchy (CX)

  • March 24, 2026
  • 2 replies
  • 32 views
J
QPN Level 4 ●●●●
Forum|alt.badge.img+8

I am trying to create a level-based CX org hierarchy that essentially acts as a parent-child hierarchy with employee/manager names listed throughout the hierarchy. The hierarchy should be based on the employee ID which will match a data field in the survey response/dashboard data set. When the hierarchy filter displays in the dashboard, the filter should display the employee names rather than employee ID.

 

We initially tried to do this via parent-child hierarchies, but that did not work for us since we wanted to be able to select the very bottom leaves/nodes in the hierarchy to view their results rather than just select managers. We switched to level-based hierarchies based on the advice here.

 

I can confirm the overall level-based hierarchy structure is working using the configuration below. A hierarchy is generated with a level for each of the 10 levels of the org hierarchy with dashboard users assigned to their appropriate level. However, the org levels are named after employee IDs rather than employee names. We want the employee names to display in the filter. 

 

I thought this could be done using the “Use Org Unit ID” option in the level based hierarchy setup (shown in 2nd screenshot), but it does not seem to work how I expected. I tried including the each level name on the left side of the configuration, and each level employee ID on the right side to act as the org unit ID. Once the hierarchy finishes processing, it is empty. There are no levels in the hierarchy and no users/employees assigned to any levels. Does anyone know how to get the CX hierarchy to work this way?

 

WORKS TO GENERATE HIERARCHY (but displays employee ID rather than name for each level name)

 

DOES NOT WORK TO GENERATE HIERARCHY (results in empty hierarchy, no levels and no users assigned)

 

April 13, 2026

Hi ​@Lpena - Thanks for the reply. You are correct, there was an issue with the IDs have a duplicate across levels. The employee at the very top of the hierarchy had their name/ID listed in both the L1 and L2 level data for themselves. They should have only been listed in L1.

Q Support was able to point to this issue, and then it was solved with the hierarchy showing all the levels after re-generating. Thank you!

 

Hey, Jake!


Dealing with those level-based hierarchies can be a real headache when they just want to show IDs instead of names. Essentially, the “Use Org Unit ID” toggle is looking for unique unit identifiers, so if those are set to employee IDs, the dashboard is just doing what it's told. To get those names showing up in your filters, you'll want to make sure your hierarchy file has the employee names as separate metadata fields. Then, you can map those names to the levels rather than using the raw IDs as the labels.

The empty hierarchy you ran into usually happens when there's a break in the chain, like a non-unique ID or a missing reference in the parent-child relationship. Double-check that your data is clean and that every ID matches up perfectly. If you’ve tried re-mapping the names and the hierarchy is still coming up blank, it might be a deeper configuration glitch. In that case, I’d suggest heading over to the Customer Success Hub at https://support-portal.qualtrics.com/ to have someone look at your specific hierarchy file. They can help spot any data mismatches that might be hiding in the rows!

 

2 replies

Lpena
Qualtrics Employee
Forum|alt.badge.img+3
  • Lpena
  • Qualtrics Employee
  • April 13, 2026

Hey, Jake!


Dealing with those level-based hierarchies can be a real headache when they just want to show IDs instead of names. Essentially, the “Use Org Unit ID” toggle is looking for unique unit identifiers, so if those are set to employee IDs, the dashboard is just doing what it's told. To get those names showing up in your filters, you'll want to make sure your hierarchy file has the employee names as separate metadata fields. Then, you can map those names to the levels rather than using the raw IDs as the labels.

The empty hierarchy you ran into usually happens when there's a break in the chain, like a non-unique ID or a missing reference in the parent-child relationship. Double-check that your data is clean and that every ID matches up perfectly. If you’ve tried re-mapping the names and the hierarchy is still coming up blank, it might be a deeper configuration glitch. In that case, I’d suggest heading over to the Customer Success Hub at https://support-portal.qualtrics.com/ to have someone look at your specific hierarchy file. They can help spot any data mismatches that might be hiding in the rows!

This reply contains AI usage for clarity and language purposes.
J
QPN Level 4 ●●●●
Forum|alt.badge.img+8
  • jake_dufinetz
  • Author
  • QPN Level 4 ●●●●
  • April 13, 2026

Hi ​@Lpena - Thanks for the reply. You are correct, there was an issue with the IDs have a duplicate across levels. The employee at the very top of the hierarchy had their name/ID listed in both the L1 and L2 level data for themselves. They should have only been listed in L1.

Q Support was able to point to this issue, and then it was solved with the hierarchy showing all the levels after re-generating. Thank you!

 

Hey, Jake!


Dealing with those level-based hierarchies can be a real headache when they just want to show IDs instead of names. Essentially, the “Use Org Unit ID” toggle is looking for unique unit identifiers, so if those are set to employee IDs, the dashboard is just doing what it's told. To get those names showing up in your filters, you'll want to make sure your hierarchy file has the employee names as separate metadata fields. Then, you can map those names to the levels rather than using the raw IDs as the labels.

The empty hierarchy you ran into usually happens when there's a break in the chain, like a non-unique ID or a missing reference in the parent-child relationship. Double-check that your data is clean and that every ID matches up perfectly. If you’ve tried re-mapping the names and the hierarchy is still coming up blank, it might be a deeper configuration glitch. In that case, I’d suggest heading over to the Customer Success Hub at https://support-portal.qualtrics.com/ to have someone look at your specific hierarchy file. They can help spot any data mismatches that might be hiding in the rows!

 

    Terms & ConditionsAccessibility statement