If adding a has many relation which points to itself, the result is 2 lists. For example: A Feature is related to other Featues (many to many). If you add this, you will get 2 relations and boths are displayed in the feature. In that special case it makes no sense to show the other way around as …

I don’t think you should select many-to-many in this case, one-to-many will be enough if you want to just have a hierarchy. In this case you will have one list.

I will give it a try and see if it works.

I suppose that there are times when it’s useful to have a ‘peer’ relationship (i.e. not directional) allowing for entities of the same type can be put in a group together. In this case, only one field is needed. But I think the next question might be, “What is the meaning of the grouping?” and if i…

Maybe I’m missing something but it seems no matter what kind of relationship I create to “self”, I always end up with two fields. Either one single-select and a multi, two multis, or two singles. Why? Maybe I don’t understand the logic of “relationship” quite well enough and what it means technicall…

Loopback Relation - hide second list?

Ideas & Features

colman November 4, 2020, 11:05pm 6

I think there are use-cases for both - but I guess this is the same issue as Basic Relation between the same Type

Topic		Replies	Views
Basic Relation between the same Type Ideas & Features	11	1446	November 6, 2020
Many-to-Many relationship in the same type Get Help	6	547	May 22, 2022
[DONE] Many-to-many relationships should be usable for levels in lists Ideas & Features list-view	24	3384	May 6, 2022
[DONE] Show related users as a relation views Ideas & Features	4	86	July 11, 2024
Recursive Groupby in Lists stop working as expected Bugs & Issues	11	230	June 6, 2024

Loopback Relation - hide second list?

Related topics