When making a dynamic relation filters, it can only use to-one relations as references and not to-many (contains any of). This is a limitation.
Use case: show all other contacts in the company when logging a call. A call can be with multiple people. Maybe from different companies. If I select one person from company x, it should then show me all other people in company x. If I then press someone on company y, it should show everyone in company x and everyone in company y.
I think this is related as well: In embedded Views, allow Filtering on Relation fields for "Is this entity"
I don’t think so. But maybe the request is unclear then.
Here’s what I mean:
This works. Contacts is many to many, Company is many to one.
When you change the company to “to-many”:
Dynamic filtering no longer works.
You’re not wrong, they are different enough (yours is about the relation/link UI and the other is about the filtering UI) but they’re both related to gaps in dynamic/context filtering so I wanted to make sure they were generally linked. I think context filtering is currently half-baked and needs major expansion/improvement.
I see, makes sense! Agreed that context it’s such big selling point of Fibery, yet the way it works right now results in a subpar experience in different areas. (Just the fact that is works in such different ways in different places)
