There is a feature request for Hierarchy views and occasional posts wanting to have some sort of organizational chart.
https://www.googlecloudcommunity.com/gc/Feature-Ideas/Hierarchy-Views/idi-p/261848
The below tip implements the hierarchy view using a table view, of course with some limitations listed below. The main idea is to selectively show the table rows based on user selection.
The tip basically visually extends the concept described in the “Team Directory” sample app (https://www.appsheet.com/templates/Teammate-contact-details-and-shared-resources?appGuidString=7ffeae20-7154-4e2c-97c5-f0b54b492540 ) to make it more presentable in a single view. So thanks are due for the concept of self referencing to the creator of sample app “Team Directory”. I have used that sample app to modify further.
Edit: (17 April 2024)
Here is the sample app
Please read the description to use various views in the app.
Please use the icons in the first column ( as highlighted below) to expand /collapse the organization of a name.
Principle
Show More
Principle: The sample app and the app in the tip has a table with a column called “Manager” that is a self reference to itself. This helps define the hierarchy structure. Of course the tip has many added functionalities ( actions, slice , format rules and some images to visually construct hierarchy structure through connecting lines)
When the user taps on the the inline action in a row, that row is selected or deselected ( by setting a column in that row). This set/reset column in is used in the slice to select/deselect the children rows where the parent ( or manager) row has been selected. The table view based on slice then presents the org structure by showing those selected rows.
There is some additional work to include images in different image columns as per hierarchy level so the org level structure is visually shown. These images also include the (grey connector lines Ͱ) that show up suitably depending on level and selection.
Link to 1 minute demo video: https://www.loom.com/share/07ee449861fb425e98d782141be575c9
A screenshot of the Org chart from the app:
Some challenges and peculiarities to note: I believe the system will work for multiple users also, as the logic takes care of storing the selection status separately based on each user. However extensive testing on simultaneous use by multiple users still remains. Should work well for a single user at a time though.
The hierarchy depends on a serial number structured column. So the addition of new team records needs to be done by only one person at a time. However I believe in most organizations , the employee table is anyway managed by a select team.
Hope this helps
