Pinging this with yesterday’s new update.
Lets imagine this scenario:
Emails ← Person ← Company
If I want to see all emails from all people in the company, I could use a lookup, but then I can’t create and its much less powerful.
Instead, right now I need to add a relation and add a context filter to show the emails from people from company. Then when I link a person to the newly created email, it doesnt even add the company!! This makes sense, as the filter has nothing to do with the company. But the thing is that then this Company → Emails relation isn’t and shouldn’t a true data relation. Just a view. Like a lookup.
So I guess this is questioning the whole deep context filter concept. If its a deep context filter, it should be just a view and not a schema relation.
Technically its just a more powerful lookup no? Shows the same data when configured…
It’s frustrating because I don’t want to add a relation field when a lookup is actually what I need. It’ll just be an empty field that can confuse people and clunks up the schema.