Cool discussion. Let me see if I understand this correctly:
Sometimes there is a need to duplicate a view a variable number of times each with a specific context. Also we need this to all display on one page.
In your example you need a calendar duplicated many times over (one for each client).
If I understood that correctly then I recall a similar idea was discussed here:
Yuri calls it Dashboard Card Stream
For your use case, adding this Card/View Stream to dashboards would solve this issue.
This configuration would look like the following:
You would have a single dashboard titled âClient Calendarsâ
On that dashboard you would add a Card/View Stream that would display a calendar view
The stream would be set up to have one calendar view per client (set as a context filter)
Does that accomplish this need? If that is the case this might be a Dashboard enhancement instead of a view enhancement.
Currently you can not have a dashboard in a Relation View, so I donât think Yuri was reffering to the term Dashboard in the Fibery sense when I look at his sketches (which are lovely, btw @Yuri_BC !!)
This is essentially adding Context Views INTO other views. So per entity in this view, I can can a view inside it. This would indeed also solve the problem, with a bit of a different approach. Drilling down instead of up. Also a possibility.
Will explain difference for clarity (using Task Calendar per Client as an example):
Above I suggested:
Create Top Level View of Task calender
Add Filter and Set it to âContext Filterâ
This will then make tabs using that fieldâs entities.
These tabs can also be filtered
Ability to convert the tabs into sections
What Yuri and Daniel are saying:
Create a List view with Clients
Toggle a mode somewhere to allow the new layout
Create context views inside each Client here.
These can be mirrored to show in all clients.
Making smart folder into a smart view so to speak.
To me dashboards seams like the place to consume multiple views. So if you wanted a view with multiple calendars you could have that. In addition to this, if dashboards can be placed inside entities then you can have the context of the entity.
Yuriâs idea, I believe, allows for adding a widget on the dashboard that is repeatable similarly to how smart folders repeat entities. Except the widget could be a view or some other defined UI.
My concept is simply to allow other views to be defined inside an entity with the context of that entity being applied. These views would be their own separate tab and behave just like smart folder views that also take on the context of their parent.
I like your idea of expanding quick filters. There is a lot that could be added there, like adding inputs or using dropdowns, Airbnb has some cool UI for filters. If you could define filters like that on a view it might help to accomplish what you are after.
Or as I think you are envisioning, you would like to have tabs on a view that switches context similarly to how reports work. Is that right?
Either way, expanding quick filters would be awesome.
The new âDashboardâ view I feel is very artificial when what we really need is for an entity to feel more like a dashboard.
Why place a dashboard inside an entity when you can just make the entity view into a dashboard? I feel like its a much more elegant solution.
The main thing Iâm trying to avoid is needing to adjust Schema and Filters after the system is set up. The tabs like in reports need to be set up manually, this means making a new tab every time theres a new client, for example. I was suggesting for there to be a way to have âSmart Tabsâ kind of.
