Skip to main content
Question

I don't see a way to create a hierarchy from a table that just shows employee and manager.

  • July 1, 2018
  • 0 replies
  • 47 views

Is there a way to handle the recursion for any number of levels, so I could have one table that has: 

employee   manager
bill              mary
mary           jane
jane            bob

and from there I can make sure that jane can see the performance review of bill, for example.  How can I start with the above table, with any number of relationships, and end with a table that has:

employee   manager1_   _manager2_   _manager3_
bill              mary           jane             bob

(As an aside, I have exactly the same problem with serial numbers on parts, that roll up to assemblies with a new serial number, but those assemblies roll together into larger assemblies with a new serial number, with N levels.)

All help greatly appreciated!
This topic has been closed for replies.

A table can be relation to itself. So 1 Manager May have many employees. Except that the managers are actually Employees.

So then the actual relationship is that 1 Employee have many Employees. The field that the system will create called [Related Employee] should be renamed to [Manager] and then it should make sense.

As for Jane seeing Bill, who is two levels down from her, I think that is possible to do.

But having said that, I�m not sure it�s intuative for users when set up that way. There is an arguement for setting it up more traditionally, where each employee has 3 slots called Manager Level 1, Manager Level 2, Manager Level 3.

Forum|alt.badge.img+5
  • Quickbase Alumni
  • July 1, 2018
Great to see your name again, Dave.
Definitely do the recursive table-to-itself relationship.
Just rename fields so your users don't get lost.
And, give us a holler at www.cloudbaseservices.comhttps://community.quickbase.com/quickbase/topics/www.cloudbaseservices.com

  • Author
  • Quickbase Alumni
  • July 1, 2018
Thanks Debbie - I very well might.  I hope you're doing well!

Forum|alt.badge.img+5
  • Quickbase Alumni
  • July 1, 2018
A few more thoughts:
  • You should only build one recursive relationship (eg employee to manager).  For additional reporting, add look-up fields (eg second level manager.)
  • When you need to change many records, create a report with the records.  Use the "More" button in the upper right hand corner of the screen to access the "Search and Replace in this report" feature.  See below.
  • Consider getting an extract from your company's HR system OR, better yet, integrate with it.  Some changes can then be automated.