Hierarchy Views

Expanding Tree - root/node style
Chart Style - Think org Structure
And as a group and sort option for drilling, tables/decks…

All we would need to do is indicate which column in the table contains the Parent Ref…
Maybe a customization on what level to start at, and hide/show “blank” levels…

Hierarchy is a easily achieved by having a REF column within that table the ties back to the same table… So the user can indicate the parent… EX: an employee table could have a REF column back to the employee table to select that person supervisor. With the Chart style view we could then look at a dynamic org chart that we can click and pan on. Or with the Tree, we could drill into it by supervisor.

@morgan Pretty Please?!
@praveen With sugar on top!

And yes, I currently “fake it till we make it” So, I’ve got plenty of creative workarounds…

Are you able to show some kind of sample?

3 Likes

image

2 Likes

It’s also great for all kinds of data not just personnel… Think project and task… Or time based, year, month, days… Or location USA > Texas > Austin… It’s an automatic ISAPARTOF…

https://docs.microsoft.com/en-us/sql/relational-databases/hierarchical-data-sql-server?view=sql-server-2017

Would like something similar for viewing parent/child relationships in a table - eg with Bill of Materials and subassemblies - similar to grouping in Excel. (Image attached just the quickest one I could find online that illustrates the usefulness). That would unlock significant power in Appsheet for us.

image

1 Like

Love it!

Grant, just a thought, if I can export mind maps to a spreadsheet, would nice to import that table into an app.

Exactly, it allows you to have undefined layers… Contract structure and cost codes is another one…

Bump, please vote. This cuts down on the number of tables you’ll probably need to get awesome drilling, and trees, and charts!

4 Likes

@morgan @praveen Was thinking back to an earlier thought of mine, but wanted to pin it here…
A specialized REF column would seal the deal “REF - Hierarchy.” This would clear up plenty of things, automatically referencing the key column of that table, and each table can only have one. Then in the group and sort we could simply select “Hierarchy”. Or maybe it still deserves it’s own fancy views?

We also need other types of REFs so maybe a ref subtype would be valuable. many to one, 1:1, and Hierarchy

2 Likes

It is a great idea!

We already can see Related List on a deck view, “Nested Table Collumn” feature. Perhaps it would be a simpler solution to just add a show/hide button for the Nested Table.

Also, if the the row height could adjust for the number of nested rows, maybe set a limit height in which the vertical scroll bar would appear, but no minimum height.

Now the rows have a fixed height, which looks strange when the Parent record have few or no Child Record (see image).

image

I’d love to use this functionality to limit what data users can see. For example, the “root” of the tree of a project is the Primary Contractor. They can hire subcontractors (child nodes), who themselves can hire subcontractors, and so on. I want any contractor to be able to open the app and see their data and data from their “descendants” (any subcontractors they hire, or that their subcontractors hire).
As of now I have an Owner app that displays data from all contractors on the job, but what I really need is a Contractor app that drills down the data.

Yes, exactly. I’m currently doing this, but it’s a bit janky and relies on spreadsheet calculations…

What kind of spreadsheet calculations allow that? I’d be very interested in trying them out.

Here’s a video of my janky stuff:
Appsheet, save me from myself!
CloudApp
@Stefan_Quartemont not sure if you have more stroke than me to get some hierarchy going on the appsheet side…

1 Like

@Grant_Stead The way I’ve always achieved this is to have a low level record have reference columns all the way up to the highest record

Ex. Task Note record: Customer ref, project ref, task ref, task note

The task note has ref all the way up to the highest tlevel item.

So I could have a ref list at customer and see all the task notes. Likewise I could give a user access to a project, and filter out the task and task notes tables to only show ones that contain the key of that project

How would you visualize the relationships in the table you’ve made?

2 Likes

The difference here is that this all references the same exact table, there aren’t multiple tables, just one… So, i’m building the same “list” concept in a fashion. The point of the feature request is two fold, one “Appsheet, hook us up with some slick views that leverage this hierarchical relationship…” and two, "Appsheet, hook us up with some slick list expressions that automatically build these lists, so they don’t have to be in my sheet. Cause even though it’s all doable, the point of Appsheet is to be no-code…

Currently I have a drill down situation. Where I manufacture a starting list view, then when you click it, you go into the detail view for that item, the detail view only has the title and then ref lists, the first list is items that are immediately below the item your in, and clicking it drills into that detail view…
CloudApp

1 Like