I have [Product] *------* [Feature]. (Features belong to products, but some features span multiple products; e.g. “2FA” is a feature of both the backend CMS and of the mobile app). There is also a [Product] ----* [Bug]. (A product can have bugs.) When I create a list, I can add Bug as a second lev…

Implemented in the latest release CHANGELOG: March 23 / Many-to-many relations in Lists and Smart Folders, Open Entities in panel from Board & Table View

Hi, Jean! The paradox is that an entity can have two parents in such situations. And it’s like with many to many - a lot of questions rendering. By the way, we can formulate the limitations of our hierarchies as follows: there is only one parent for an entity. This also explains why only the top t…

[image] CHANGELOG: February 25 / Hierarchical Lists (beta), some improvements Changelog My request is to support many to many relationships. In this example I’m only referencing types imported via the JIRA integration. There are no single selects utilized for the JIRA inte…

[image] jean1: Features belong to products, but some features span multiple products; e.g. “2FA” is a feature of both the backend CMS and of the mobile app This is exactly the kind of problem that I have with Fibery’s views. It isn’t just the list view, but also smart folders, and boards. Fib…

I don’t understand why there must be the limitation that lower-levels of a hierarchical list cannot also be recursive/hierarchical, when the entities adhere to a strict tree structure: Here is a my hierarchical list: [image] The “Page” type is self-referential with a strict parent-child relations…

Is it (or will it be) possible to duplicate and customize a Hierarchical List view via an Automation action? I don’t see any support for Views in the API. If we will have the ability to customize entity views/dashboards, then this may not be important. Otherwise it is. Can an Action button (e.g. …

In your example, a Page could be a child of a Project and a child of another Page. It seems that Fibery can’t cope with an entity appearing in two different places in the same list view. Who knows the underlying technical reason why :-/

[image] Chr1sG: Fibery can’t cope with an entity appearing in two different places in the same list view Many cases, including my data, should never have that occur, because I want to model a strict tree structure. But it still could occur, as Fibery does nothing to enforce such relationship …

As you propose, this is a constraint that would need to be set up at the Type definition. And thus would be enforced when someone try to add a child that is already in the parent hierachy, thus preventing cycles. The View has nothing to do with that, Views cannot enforce the model constraints. So t…

Indeed, the limitation of many views to only one-to-many relations is a bit frustrating :frowning:

[image] Polina_Zenevich: The paradox is that an entity can have two parents in such situations. I don’t think that’s so bad — it will just show up more than once in the list …

[DONE] Many-to-many relationships should be usable for levels in lists

Ideas & Features

Chr1sG May 23, 2021, 7:03pm 3

Topic		Replies	Views
CHANGELOG: February 25 / Hierarchical Lists (beta), some improvements Changelog	28	3105	June 7, 2021
Representing nested relations Ideas & Features	31	3736	February 12, 2026
Relationship properties Ideas & Features flexible-domain	42	3164	March 10, 2026
Recursive Groupby in Lists stop working as expected Bugs & Issues	11	234	June 6, 2024
Filtering "Collections" Sub-entity views - Request, and is it done? Ideas & Features	17	1805	September 27, 2022

[DONE] Many-to-many relationships should be usable for levels in lists

Related topics