Two-Way Relation Properties
Category: Data Model / Relations
Summary:
Request to add support for automatic 2-way relation properties across objects. Currently, relation properties in Anytwo operate as 1-way backlinks. When Object A links to Object B via a relation property, the inverse relation property on Object B's page remains "Empty".
Use Case & Example:
Suppose you have an Area object ("Home & Garden") and a Task object ("Finish Report"):
- In the Task object, you set its "Area" relation property to "Home & Garden".
- With 2-Way Relations, the "Tasks" relation property on the "Home & Garden" object page should automatically fill with "Finish Report".
The same applies to Books & Authors ("Written By" <-> "Works Created"), Projects & Areas ("Area" <-> "Projects"), etc.
Why This Is Important:
- No Manual Double-Entry: Users don't need to manually link objects from both sides.
- Object Page Integrity: Opening an Area or Project page instantly shows all connected Tasks, Notes, Bookmarks, and Items in its property fields.
- Relational Parity: Provides the seamless relational database experience users expect from modern PKM/workspace tools.
2 Comments
Sign in to comment
Adding to this, while I like the backlinks drawer, having a property set to bi-directional linking would be extremely useful.
I use AnyType primarily to worldbuild. I have 400+ characters with a growing cast/expanding families. I use bi-directional links for a ton of other stuff (locations: country <-> state <-> city; magic systems: main magic type <-> subtype; just to name a few), but the following is the easiest case: I have "cousin," "grandparents <-> grandchildren" "parents <-> children" properties in AnyType that would be great if I have 2 options:
a) A single relation property that is self-referential: If I set Character A's "Cousin" relation property to have Character B, Character B's same "Cousin" property automatically fills in with Character A, without the need to create a second relation property
b) if I decide that I DO want 2 relation properties, like in the case of parent <-> child, if I set the "Parent" property for Character A to have Character B, Character B's "Child" relation property should automatically be set to include Character A.
I support this. It would simplify managing relationships between objects. That said, there is also a need for a one-way link feature.