Works that way by default.

Then I must have it turned off because it’s not working for me. Is there a setting somewhere I can check?

Cat,

Cross-linking is automatic. Check if the field is “hidden” (Hide fields).

Nope.

Looks like it is working as intended in your video. The records are linked.

What specifically are you trying to accomplish?

In this table I have linked the polish Ursula to the polish Jafar (in the same table) using the Others in Collection field. When you look at the Jafar card, it does not link back to Ursula. I want each individual polish in a collection, to link to every other individual polish in that collection. But I don’t want to have to do it by hand.

I see, in the same table the link is not bidirectional. Could you have a Collection table to relate those polishes?

I have a collection table with the name of the collection and all of the polishes in that collection, some of which I do not have.
Is there a way to make links in the same table bidirectional?

Very glad to see same-table Rollups, but the bidirectional linking is crucial to maximize the feature. Please prioritize this!

I’m going to put my bid in on this feature as well. it would fix a major hole in my work flow…

really need this too…

I really really need this. Can no one think of a suitable work around?

I need this too - very hard to work around

Absolutely necessary.

Just re-built my entire Base (again) because working around this missing feature became such a tangled mess since I can’t have categories with entries that link back other entries in different categories in the same table.

EG:
People Table:

Name | Student/Teacher | Taught Students | Had Teachers
Mark | Teacher         | Billy, Jane     |
Billy| Student         |                 | Mark
Jane | Student         |                 | Mark, Sally
Sally| Teacher         | Jane            |

YES PLEASE. I’m using the Product Launch template, which has the “Blocked by” field, and when a task is complete, it would be great to have an automatically generated “Blocker for” field, a list of tasks blocked by that task, so I can move on to working on those.

The simple solution here would be to add a simple switch to allow bi-directional linking on self-linking linked record fields. For example, let’s say I have an Inventory table and a Packed With linked record field pointing to the same Inventory table, I’d like a toggle switch in the linked record field’s options to allow bi-directional linking (it’s a major pain to have to go to both records and add these in manually!!!). There are many clear use cases to allow users to choose how the linked record field should behave on self-linking linked record fields.

Any update here? @Katherine_Duh

bidirectional linking in obe table is also wanted here

Darn, I was wanting a way to link referred customers to each other without having to have two separate tables. This needs to be a thing!

I’m adding my vote here. I’m assigning issues to user stories which are stored in the same table, but I can’t see which issues belong to a story.

Would be better to have Stories and Issues tables, not?

Often, issues and stories need to be prioritised against each other. Also, an issue can sometimes turn into a story when reviewing them with the team. For these reasons, I have them in one table.

Adding my voice to the masses too. This feature would be amazing for my lightweight CRM.

Really need this too!

Adding my vote too :exclamation: Notion has this.