In a view, you can select a database and group by a field. This makes the grouped by field the top level of the list/table etc.
If Entity A belongs to User A, I want them to be able to see it in the smart folder.
However, I want the top level to be grouped to pre-filter entities into smaller categories (less visual clutter).
It seems this isn’t currently possible. Is there any way without major changes occurring to get this behaviour to work in this way?
And before you say, “Create a new database and change the field, then make the smart folder based off this new database”—I can’t. It would screw up a ton of automations. Also, it wouldn’t hide items with no relations (or that have been filtered based on access levels for the active user).
I don’t see how what you are suggesting has to do with my post
If I have a select field called “Happy and you know it” with options “clap your hands”, “stomp your feet” and “shout ‘hooray’”, I can’t make these top-level smart folder elements for grouping purposes.
Even if those options were their own database, it still wouldn’t work because I care about what they are attached to, not the classification itself.
And I can’t hide ones where the relationship is empty. If top level is “Happy and you know it” database, even filtering “where field is not empty” doesn’t work because it needs to be RELATIVE to the logged-in user. There could be a hundred classifications for the “Happy and you know it” database, but only 3 are relevant to user A, 6 for user B, etc.
I didn’t know if you were using a select field or a relation. That’s why I asked about relations.
If grouping were via a db (and not a select field) you could use a lookup on this db to get the Users who are linked to the nested items, and then set a smart folder filter on the lookup.