Forum Discussion

Orange's avatar
Orange
Regular Visitor
6 years ago
Solved

Creating hierarchical Thingy from Field

  I am working with an Employee Directory data set. One field is called [Company_Org_Path]. Each employee record has this one field that shows the Organization Path they are in. The organization pa...
  • Anonymous's avatar
    Anonymous
    6 years ago

    So I work in a company with a sizeable number employees as well.  We too have a hierarchy like what you describe.

     

    I've built my Org hierarchy with the levels each becoming a column.  I would suggest making more columns than you think you need as the reorganizations can suddenly collapse or expand without notice. :)

     

    I've built them as you say in option 1, where you have them null'ed if not needed.  The main reason I do this is to do all sorts of other analysis where you get to view information about either the individual, their # of employees under them (directly or indirectly), and then the org analyses, like # divisions per business, # teams per business, etc.  

     

    Then the employee analysis like how many janitors does division 1 need, vs. division 2....etc.

     

    I have a master table of all the organizations in the company, which I use to merge with other queries when I have a subset of information (like an employee ID), and then want to use that for filtering.  Think building, floor, city, state, country, permanent or temporary employee, returning vs. first time employed at the firm, etc.  Lots of uses.

     

    hope this helps.