Paired self-table record links. Ie Parent/Child type links


#1

I’ve posted on this before. But seen no activity on it. I need this, soon if possible, because every single base of mine relies on this functionality.

I REALLY want a link-to-record within the same table to create another link column that auto-populates. Or a type that will.
I just spent all day trying to fudge around it, but it requires either (a) manual linking with every record, (b) at least two new columns on this and a completely separate table to copy/paste/formula, that requires basically a temporary duplicate entry and again, lots of manual entry. And this doesn’t update with new records.

I’d love a hierarchically-grouped view, but I could make do with just this one feature;
I want a second column to be created when I self-link a table!!

Does anyone have a self-updating workaround to this? Because for the life of me I can’t find one. And I don’t want to fiddle around with Zapier, either, because any solution I can think of with that requires a paid account.

Edit:
For now I’ve settled with putting each level of hierarchy on a new table, and I can sort of see them grouped in a hierarchical format.
With this (Probably the intended) use case, allowing lookups/rollups to pull actual linked records of linked records, so you can click through, would basically solve my problem.


#2

Hi Jason,
What are you really trying to accomplish, not the technical, but the functional. From what I see, you’re trying to create a relationship or hierarchy within one table. Can you give more detail on the application and what you’re trying to accomplish from a functional perspective?

Seems like I’m missing something but could you just create a series of categories and then group on the categories? This would give you the visual drill down I think you’re looking for. The categories could be driven from other tables which are just summaries of the key table you’re talking about.

Please provide some more functional details.
Pierce


#3

I have used series’ of groups as well as tables for this.
The use case tends to be where it’s a more specific type of the same kind of item, that has all of the same points of data. Either way above, this becomes quite a chore to ender data manually.

For example; For my art studies I have a list of animal types/species, and the variables I use to classify them are the same; but some are subspecies of others, or have very similar body types.
Similarly, I have a set of ‘aspects’ I can use that nest like that - for creation of fantasy creatures, etc.
Another list is of professions per time period to study; overlapping mediums, locales, roles, etc. are all ideal for tables. But nested by social rank, or specification, is more difficult.