C.c
January 24, 2026, 4:03pm
4
If you dig down the posts in that feature requests, starting from Post 28 , you would see advanced filters on querying with relation, but if you have really checked, then with all respect, we can keep this as a separate request.
Have fun with relations.
Other related discussions/requests:
Hi !
I’m designing a system to track Entities (e.g., projects, locations) and Elements (e.g., equipment, tools), where the same Element can be linked to multiple Entities—but each link needs to store custom attributes (e.g., a unique image, notes, or status for each Entity-Element pair).
Current Approach
I’m using a “join object” (inspired by relational databases) to represent the relationship:
Entity type: Represents the main object (e.g., “Project A”).
Element type: Represents shared i…
Ever since the introduction of “relations as objects” and also “inline sets” into Anytype, I was toying with the idea of incorporating more and more aspects of my life into Anytype but in doing so as I mentioned in my other posts , I felt some limitations and lack of features can get in the way of that. Browsing through the community, I came across some interesting and brilliant ideas (multi-type and inheritance ) of what could be the next step for the “object, relations, sets” philosophy of Anyty…
Overview
The two features that create the most excitement to me are Multi-types and Inheritance, two features hightly interrelated.
In a comment by @ignatovv , he said that the Team wants to introduce Multi-Types and in the last Townhall a dev talked about working in some small feature requests as extendable objects after the open beta (iirc). In case the team had to prioritize one of these, which one would you choose?
Inheritance:
Inheritance, a widely recognized principle in software develop…